Hi Martijn
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
Hey there,
Roger Ineichen wrote:
[snip]
I don't like that. Probably we should use the existing devmode or
something like that? Devmode whould allow us to use it at
runtime and
during
Martijn Faassen wrote:
Besides an
import checker you'd need a system that would be able to thrawl through
a ZODB and report deprecated classes. The drawback is that it'd need to
thrawl through a ZODB, so that's rather costly.
Thrawl = thrashing crawl? Never heard that word before, but
Shane Hathaway wrote:
Martijn Faassen wrote:
Besides an
import checker you'd need a system that would be able to thrawl through
a ZODB and report deprecated classes. The drawback is that it'd need to
thrawl through a ZODB, so that's rather costly.
Thrawl = thrashing crawl? Never heard
Hey there,
Roger Ineichen wrote:
[snip]
I don't like that. Probably we should use the existing devmode
or something like that? Devmode whould allow us to use it at
runtime and during testing. What about a deprecation mode?
I really like to use such deprecation messages in production too.
I
On 2008-12-22 18:48:47 +0100, Martijn Faassen faas...@startifact.com said:
Hi there,
All right, I was getting a bit confused when it appeared you were
arguing against moving things at all, but you're basically in favor of
leaving the old APIs intact without explicitly breaking them.
I
Hi Christian
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
On 2008-12-22 18:48:47 +0100, Martijn Faassen
faas...@startifact.com said:
Hi there,
All right, I was getting a bit confused when it appeared you were
arguing against moving things
Hi there,
All right, I was getting a bit confused when it appeared you were
arguing against moving things at all, but you're basically in favor of
leaving the old APIs intact without explicitly breaking them.
I think we need to think of some way to signal that the preferred
import location of
Hi there,
Tres, please tell me what I should be doing as opposed to moving
things around and deprecating them.
I want a version of Grok with far less dependencies than it pulls in
now. I believe there are a lot of advantages in doing that, and I'm
not going to go into them here as I'm sure you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hi there,
Tres, please tell me what I should be doing as opposed to moving
things around and deprecating them.
I want a version of Grok with far less dependencies than it pulls in
now. I believe there are a lot of
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
If we that there is a real goal other than future
cleanliness for the deprecation system, then a system which
requries warnings to be explicitly enabled (e.g., via a tool,
or an environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
If we that there is a real goal other than future
cleanliness for the deprecation system, then a system which
requries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
One issue is that adding deprecation messages for importing
symbols from the old makes all downstream code add ugly BBB
Hi Tres
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
[...]
One issue is that adding deprecation messages for importing
symbols from the old makes all downstream code add ugly BBB
warts in order to suppress them when run against multiple versions.
Yes
Hi Christian
Betreff: Re: [Zope-dev] Deprecate ITerms in zope.app.form?
[Re:zope.browser?]
On 2008-12-15 13:44:43 +0100, Roger Ineichen
d...@projekt01.ch said:
Hi Christian
Betreff: [Zope-dev] Deprecate ITerms in zope.app.form? [Re:
zope.browser?]
[...]
A deprecation
14 matches
Mail list logo
