Adam GROSZER wrote:
> Someone releases a new package version and your project just break the
> next day. That's a nightmare.
That shouldn't happen with individual package releases where releases
are done sensibly.
(ie: if you're going to do a big backwards-incompatible release, let
people know. If you rely on a package, put in some sensible version
constraints in your setup.py, if your *project* (rather than your
packages) is paranoid (and it should be!) then lock the versions you use
down in something project-specific like a buildout.cfg, if you use buildout.
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
