I've learnt a lesson re. configuration management.
When setting up new projects, esp. projects built on frameworks like TurboGears, you should keep your eggs handy, for all possible platforms.
an "easy_install TurboGears==1.0.1" in September will not necessarily download the same code in October. In particular, it seems RuleDispatch has changed, which exposes a new bug in my application... grrr.
Subscribe to:
Post Comments (Atom)
Popular Posts
-
These are the robots I've been working on for the last 12 months. They each weigh about 11 tonnes and have a 17 meter reach. The control...
-
So, you've created a car prefab using WheelCollider components, and now you can apply a motorTorque to make the whole thing move along. ...
-
I have just spent an hour trying to track down a weird bug in some Javascript interpolation code. The offending code looks like this: var n ...
-
Why would I ask that question? Python 3 has been available for some time now, yet uptake is slow. There aren't a whole lot of packages i...
-
Dear Lazyweb. Imagine a nice RESTful interface for working with Tags. The URL: /tags/ will return a list of all the tags. The URL: /tags/fo...
-
After my last post, I decided to benchmark the scaling properties of Stackless, Kamaelia, Fibra using the same hackysack algorithm. Left axi...
-
I've just uploaded Fibra 2 to the cheeseshop. Fibra 2 includes the promised non-blocking plugin, which allows a generator based task to...
-
The procedural planet package has been updated to version 1.4, and you can see the new demo here . It features better city light control, be...
-
I've just finished refactoring an awful C# class. I had been delaying the job for a while because I didn't want to do it. Then, whil...
-
I've built sites with Django, TurboGears and Pylons. I've come to prefer Pylons. Why? Pylons gets out of the way, and stays out of t...
3 comments:
Can't you note the version of RuleDispatch on one machine, install the same on another, and then install TurboGears? RuleDispatch is a separate package. No wonder the same version of TurboGears can pull up a version of RuleDispatch different from the one it would have pulled a month ago.
Also, you can record the exact versions of required packages in your own application. The install_requires argument of setuptools.setup allows that.
Yep, thats true. In this case however, it seems that RuleDispatch eggs don't seem to hang around long, so when easy_install RuleDispatch==the_version_i_need, setuptools reports that it can't satisfy the requirement. Hence the argument for keeping copies of the eggs yourself.
Agreed, TurboGears packages RuleDispatch themselves so you're at their mercy :-). Using install_requires would at least provide for a "clean failure."
Post a Comment