We all know and love "python setup.py devel". But sometimes its usage
leads to strange and hard to track effects.
For example I was just testing a current branches/1.0 checkout and when
I was doing "setup.py" install I was noticing that it was pulling the
"Extremes" package as a new requirement, which I had never seen bevor.
I found out, that this is required by the latest RuleDispatch dev
package (r2506), which got pulled, because I didn't tell "setup.py
devel" to look on the turbogears.org for egg packages. The pre-compiled
RuleDispatch egg (r2306) on turbogears.org, which fulfills the current
TG requirements, does not require "Extremes".
Bottomline is, when you want to test your checkout, create a new
virtualenv and then do
python setup.py install -f http://turbogears.org/download/
to get an environment that matches as closely the one a user installing
via tgsetup.py will get.
Unfortunately, it is not possible yet to specify any extra requirements
(like in "TurboGears[testtools]"), so when you install any optional
requirements manually via easy_install, you must always manually look up
and use the version contraints from TruboGears's setup package.
Does anybody have any ideas how to handle this in a better way?
Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
