Christian Theune wrote:
Martijn Faassen schrieb:
[snip]
I think the explicit versus implicit discussion has no place here.
Placing a package on the 'develop' line is a very explicit action, and
you place it on that line because you want to *develop on it*. Having
another package being picked up is surprising.
OTOH it makes you aware about potential version mismatches very early,
because you try to develop on a package that doesn't seem to be
supported by that particular buildout. So maybe you, for example
actually wanted/should increase the version number.
I don't understand what you're getting at. A development package will
*never* be supported by a package listing in a particular buildout, as
it should always have a 'dev' marker in its version number in setup.py.
If it's listed in any list of fixed versions, it's always going to be wrong.
And yes, when you release a package you've been developing you do need
to update the versions listing of the buildout that depends on it. It's
clear enough from what's listed in 'develop' what you need to be updating.
Did really nobody run into this surprise before? I am really surprised
at that. I mean, you were working with a buildout with a fixed version
list, added a package to 'develop' and then (after some head-scratching)
noticed your changes weren't being picked up at all, and then you
*weren't* surprised about it and wondering what to do about it?
Regards,
Martijn
_______________________________________________
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 )
