[Framework-Team] Re: pyflakes? (was: Re: Translation effort for Plone 3.1)
florian.schulze at gmx.net
Fri Feb 1 14:29:11 UTC 2008
On Fri, 01 Feb 2008 14:34:01 +0100, Andreas Zeidler
<az at zitc.de> wrote:
> On Feb 1, 2008, at 2:24 PM, Wichert Akkerman wrote:
>> Previously Tom Lazar wrote:
>>> given the aforementioned possibility of 3rd party breakage i think
>>> it's plain that 'pyflakes sanity' is a no-go for 3.1 but perhaps for
>>> 4.0? since that will necessitate 3rd party rewrites/adaptions anyway,
>>> might as well throw in pyflakes sanity, as well.
>> You may need to properly deprecate things before removing them.
> hmm, unused imports? that might be a bit too much, no? i mean, i'd
> go ahead and remove any import statements i'm not using anymore in my
> packages, and that should be okay. imho, the only trouble are
> interface packages, otherwise people shouldn't import package a from
> package b anyway, but import it from a directly.
> so, how about this? deprecating imports in interface packages, which
> are not used in plone core, is okay as well as removing unused import
> from any other package? that's talking 4.0, of course... hmm, or
> maybe this could be a 3.2 PLIP, too, so we can deprecate things
> earlier. i mean, this policy shouldn't break anything provided all
> tests are passing. thoughts?
I would deprecate ones which may be used in other packages for one major
release and two major releases for the ones which affect persistent
objects, because otherwise it's a pain to migrate.
More information about the Framework-Team