Hey,

Stephan Richter wrote:
[snip]
> I have been following this discussion and just want to mention that I fully 
> agree with Roger. If you release a final version of Zope or a package that 
> spews deprecation warnings or has not fixed the imports, then this should be 
> considered bad releasing.

I'm not sure I understand this. If you are releasing a final version of 
zope.app.component, do you want it *not* to spew deprecation warnings?

Or do you mean you require someone to go through all packages that may 
depend on zope.app.component and change the imports there before 
zope.app.component is released? But if so, you'd need to release 
zope.app.component with deprecation warnings.

Several times in the previous discussion I heard people talk about 
wanting to support multiple releases of a single package and not wanting 
indirect deprecation warninsg. I'm not going to defend their view here 
myself, but I must note we've been spending some months now moving away 
from zope.deprecation.

I highly doubt that this will hurt us seriously in the coming years. And 
if it does, at least we'll be using Python imports amenable by analysis 
by any Python programmer, with records in the CHANGES.txt that can be 
read by anyone, and not our own home-grown import system using module 
proxies.

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 )

Reply via email to