Open Stack

Hi Monty,

On 09/24/2013 09:44 AM, Monty Taylor wrote:
> Instead of:
> 
> "python setup.py install"
> 
> Run:
> 
> "pip install ."

No way that this happens on the packaging side. Buildd have no network
access (on purpose), and we must not do any network access when building.

So I wonder what this post is trying to achieve.

On 09/24/2013 09:44 AM, Monty Taylor wrote:
> It is common practice in python to run:
>
> python setup.py install
> or
> python setup.py develop
>
> So much so that we spend a giant amount of effort to make sure that
> those always work.

Please continue to spend "a giant amount of effort" to make sure that
python setup.py install works (I won't care about develop), as this is
what is being used by debhelper by default.

On 09/24/2013 09:44 AM, Monty Taylor wrote:
> It should have the exact same result, but pip can succeed in some
> places where setup.py install directly can fail.

If "setup.py install" fails, this is a bug and it shall be fixed. :)

Cheers,

Thomas