On 2009-9-10 23:24, Benji York wrote: > On Thu, Sep 10, 2009 at 5:20 PM, Wichert Akkerman<[email protected]> wrote: >> On 2009-9-10 22:23, Benji York wrote: >>> 2) if you accidentally make a trunk release no one will accedentally use >>> it >>> because it will be the "oldest" release on PyPI instead of the newest, >> >> Doesn't it break all versioned dependencies on that package? > > I don't understand the question, so I'll say "no". ;)
Suppose you are working on an app which includes a package that depends on A >= 2.1 to make sure it can use a new API introduced in A 2.1. If you then add a develop egg for A to do some work on it things break with this policy because it will have version 0 and can no longer satisfy the >= 2.1 requirement. Wichert. -- Wichert Akkerman <[email protected]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
