Deployment, setup.py and index-url: What works and what doesn't?

[Moritz Schlarb]

Hi there group,

Now back to the question that you all must love the most:

What are the currently working possibilities to make an application
package with TurboGears2 (>=2.1.4, <=2.2.2) and dependencies from
outside the private package index install cleanly and nicely (from a
repository checkout at least) using "python setup.py develop" and/or
preferrably "pip -e ."?

My working workaround in most cases is to first do "pip install -i
http://tg.gy/current tg.devtools" and then a "pip install -e ." (while
having http://tg.gy/current in the dependency links of setup()).
This leads to working results - especially no problems with WebOb.

I have yet to find a solution that would work without first installing
tg.devtools.

Please share your working approaches with me and the rest, maybe we even
find something that we could call "best practice"...

Cheers and happy easter,
Moritz

[Alessandro Molina]

Yes, due to the way the private index doesn't work (yes, I wrote doesn't) you must install tg.devtools first and then perform "setup.py develop" or "pip install -e ."

I don't think there is a place in documentation where a different procedure is explained.

Doing otherwise has issues due to the way private indexes are followed, so the Pylons private index messes with the TurboGears one.

I hope with 2.3 this will solve as we don't have Pylons private index anymore in the process.

--
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbogears+...@googlegroups.com.
To post to this group, send email to turbo...@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Moritz Schlarb]