Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Martijn Faassen
Hi there, On Fri, Feb 6, 2009 at 12:10 PM, Dan Korostelev nad...@gmail.com wrote: [snip] For ZODB objects I think its okay for now not to use deprecations and to use the upgrade tool, but for the imports of other things that were moved elsewhere, I still think we need to bug developers that

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Dan Korostelev
+- Make ``class`` directive schemas importable from old location, + raising a deprecation warning. It was moved in the previous release, + but some custom directives could possibly use its schemas. Out of curiosity, *was* it used by custom directives that you know of? Well, I personally

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Martijn Faassen
Hey, On Fri, Feb 6, 2009 at 11:32 AM, Dan Korostelev nad...@gmail.com wrote: [snip] Okay, reuse of directive definitions and implementations is more widespread than I thought initially. Which is silly of me, as Grok itself also reuses directive actions (but not definitions) in some places. But

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Dan Korostelev
2009/2/6 Martijn Faassen faas...@startifact.com: Yep. Also, as I said before I think we also need to use deprecation warnings for imports that are not classes for persistent objects (until Chiristian writes the tool to upgrade them :)). As far as I understand in a recent discussion people

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Korostelev wrote: 2009/2/6 Martijn Faassen faas...@startifact.com: Yep. Also, as I said before I think we also need to use deprecation warnings for imports that are not classes for persistent objects (until Chiristian writes the tool to

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Martijn Faassen
Hi there, On Fri, Feb 6, 2009 at 5:47 PM, Tres Seaver tsea...@palladion.com wrote: [snip] Martijn hoped for a tool which would help developers find places in their code which used the BBB locations, in order to help them modernize. And to repeat, this tool was mostly created last week in the

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-06 Thread Dieter Maurer
Dan Korostelev wrote at 2009-2-6 14:10 +0300: ... I still think we need to bug developers that they need to upgrade their code with deprecation warnings, so we can eventually remove old imports. When you abuse deprecation warnings for minor cosmetic issues you risk that deprecation warnings are

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.

2009-02-05 Thread Martijn Faassen
Dan Korostelev wrote: Log message for revision 96156: Please, don't just remove things that could be used in users code. Changed: U zope.app.component/trunk/CHANGES.txt U zope.app.component/trunk/src/zope/app/component/metadirectives.py -=- Modified: