Hi there,
Baiju, much thanks for looking into this. I hope we can indeed get rid
of this code.
I myself have the suspicion that the deprecation system is perhaps a
'false optimum' in most cases. Putting in deprecations tends to be quite
a bit of work (as it's a code change), the warnings weren
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> On Thu, Mar 5, 2009 at 11:26 AM, Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Baiju M wrote:
>>> Hi,
>>>
>>>zope.deprecation is used in zope.configuration *only* to turn
>>> off deprecation warning
Baiju M wrote:
> I have pasted the relevant code here:
>
> def resolve(self, dottedname):
> """Resolve a dotted name to an object."""
I wonder why zope.dottedname isn't being used here either?
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.s
On Thu, Mar 5, 2009 at 11:26 AM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Baiju M wrote:
>> Hi,
>>
>> zope.deprecation is used in zope.configuration *only* to turn
>> off deprecation warning when accessing attribute of an object in
>> one place. But there is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> Hi,
>
>zope.deprecation is used in zope.configuration *only* to turn
> off deprecation warning when accessing attribute of an object in
> one place. But there is no test case or comment about when such
> a warning will occur.
>
Hi,
zope.deprecation is used in zope.configuration *only* to turn
off deprecation warning when accessing attribute of an object in
one place. But there is no test case or comment about when such
a warning will occur.
I have pasted the relevant code here:
def resolve(self, dottedname):
