> My point is, as a matter of *policy*, nothing should be released that
> uses deprecated stuff. I can't create a bug report about wrong (or
> incomplete) policies.
Sure you can. Write a bug report asking that PEP 4 gets amended with
specific wording.
Not that PEP 4 is followed in practice at al
On Fri, Feb 19, 2010 at 5:41 PM, Mike Klaas wrote:
> On Fri, Feb 19, 2010 at 9:03 AM, Sjoerd Mullender wrote:
>
>> The policy should also be, if someone decides (or rather, implements) a
>> deprecation of a module, they should do a grep to see where that module
>> is used and fix the code. It's
On Fri, Feb 19, 2010 at 9:03 AM, Sjoerd Mullender wrote:
> The policy should also be, if someone decides (or rather, implements) a
> deprecation of a module, they should do a grep to see where that module
> is used and fix the code. It's not rocket science.
I'm not sure if you're aware of it, b
On 2010-02-19 16:23, Nick Coghlan wrote:
> Sjoerd Mullender wrote:
>> My point is, as a matter of *policy*, nothing should be released that
>> uses deprecated stuff. I can't create a bug report about wrong (or
>> incomplete) policies.
>
> The policy is more that the test suite shouldn't raise Dep
Sjoerd Mullender wrote:
> My point is, as a matter of *policy*, nothing should be released that
> uses deprecated stuff. I can't create a bug report about wrong (or
> incomplete) policies.
The policy is more that the test suite shouldn't raise Deprecation
Warnings unless it is explicitly checking
On 2010-02-19 14:45, Eric Smith wrote:
> Sjoerd Mullender wrote:
>> On 2010-02-19 14:10, Guido van Rossum wrote:
>>> Isn't mhlib itself deprecated? (It's gone in Py3k.)
>>
>> I wouldn't like that, but it is beside my point. If a module is
>> deprecated, then it should not be used in released code.
Eric Smith trueblade.com> writes:
>
> This is because no one has gotten around to it. Create a bug report for
> it, and preferably attach a patch with tests.
>
> Eric.
>
Actually, it gives py3k warning about "mhlib" + 2 others warnings:
./python/release26-maint/ $ ./python -Wd -3 -c "import
On Fri, Feb 19, 2010 at 08:40, Sjoerd Mullender wrote:
> On 2010-02-19 14:10, Guido van Rossum wrote:
> > Isn't mhlib itself deprecated? (It's gone in Py3k.)
>
> I wouldn't like that, but it is beside my point. If a module is
> deprecated, then it should not be used in released code.
> If mhlib
Sjoerd Mullender wrote:
On 2010-02-19 14:10, Guido van Rossum wrote:
Isn't mhlib itself deprecated? (It's gone in Py3k.)
I wouldn't like that, but it is beside my point. If a module is
deprecated, then it should not be used in released code.
If mhlib is deprecated, it doesn't tell you about i
On 2010-02-19 14:10, Guido van Rossum wrote:
> Isn't mhlib itself deprecated? (It's gone in Py3k.)
I wouldn't like that, but it is beside my point. If a module is
deprecated, then it should not be used in released code.
If mhlib is deprecated, it doesn't tell you about it. mhlib uses
multifile a
Isn't mhlib itself deprecated? (It's gone in Py3k.)
On Fri, Feb 19, 2010 at 4:33 AM, Sjoerd Mullender wrote:
> I have noticed that deprecated stuff is still being used in the standard
> Python library. When using modules that contain deprecated stuff you
> get a warning, and as a mere user there
I have noticed that deprecated stuff is still being used in the standard
Python library. When using modules that contain deprecated stuff you
get a warning, and as a mere user there isn't much you can do about that.
As a general rule, the Python standard library should not use deprecated
construc
12 matches
Mail list logo
