Hi Mike,
Thanks for the report. The problem was caused by changes in how I
generated version numbers for some of the dependencies -- instead of
1.0.r100 (note the 'r' prefix for revision number) I was doing 1.0.100
(no 'r'). This caused problems when releasing minor versions such as
1.0.1 because a version '1.0.1.200' is considered lower than '1.0.100'
and thus the older version was treated if it was newer. I've fixed
this by fixing and bumping version numbers for affected libraries and
by making Reaction explicitly depend on those newer versions, so it's
fixed in trunk. I also did a 0.2.2 release just for this fix:
http://pypi.python.org/pypi/Reaction/0.2.2Anyway, just update Reaction and it should all get fixed.
Regards,
Sergey
> --
> Mailing list: http://groups.google.com/group/better-python
> Unsubscribe: better-pytho...@googlegroups.com
--
Best Regards,
Sergey Schetinin
http://self.maluke.com/ -- My articles and open-source stuff
http://www.maluke.com/ -- My commercial software and custom development services