This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Test suite emits many DeprecationWarnings when -3 is enabled
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: 7832 7849 Superseder:
Assigned To: ezio.melotti Nosy List: amaury.forgeotdarc, barry, benjamin.peterson, brian.curtin, eric.araujo, esam, ezio.melotti, flox, jcea, pitrou, rhettinger
Priority: high Keywords: patch

Created on 2009-10-09 14:30 by exarkun, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
test.log exarkun, 2009-10-09 14:30
stderr.log pitrou, 2009-10-14 19:20
issue7092_without_7832.diff flox, 2010-03-09 07:08 Patch, apply to trunk
Messages (67)
msg93795 - (view) Author: Jean-Paul Calderone (exarkun) * (Python committer) Date: 2009-10-09 14:30
If the test suite is run with -3, many deprecation warnings are
reported.  Quite a few are generated by code in the tests themselves,
but many are from constructs in the stdlib which are different or no
longer supported in 3.x.

Even aside from the fact that many of these warnings being caused by
code which I think many people would agree is not ideal, I think it is
important for these warnings to be fixed for Python 2.7.  Since the 3.x
porting guidelines recommend that projects first run their test suite
with -3, these warnings are going to be generating extra noise for
developers to filter through when they try porting their code to 3.x. 
They shouldn't need to wade through stdlib warnings to find warnings
about their own code.

Attached is a log of a complete test run with -3.
msg93800 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2009-10-09 15:15
I don't think it's so important that tests not raises -3 warnings, but
that the stdlib doesn't.
msg93805 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2009-10-09 18:21
I agree with Benjamin. We shouldn't release 2.7 w/ any of the standard 
library itself generating a Py3kWarning, but that should not apply to the 
test suite.

I have made this a release blocker until we can create separate issues for 
the modules that are emitting the warning.
msg93806 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-10-09 18:29
FWIW I tried to filter out the test-related warnings using the following
command line, but it didn't work (nothing was filtered out):

$ ./python -3 -W 'ignore::DeprecationWarning:test:0' -m test.regrtest
msg94012 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-10-14 19:14
I've fixed a bunch of them: aifc (r75407), test_atexit (r75408), bsddb
(r75409), test_calendar (r75410), StringIO (r75411), socket (r75412),
sndhdr (r75413), test_memoryio (r75415), test_profilehooks (r75417),
test_random (r75419), httplib (r75420), uuid (r75421).
msg94015 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-10-14 19:20
Here is a record of stderr after a new regrtest run.
msg94016 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-10-14 19:21
(interestingly, one of the culprits for py3k warnings is lib2to3)
msg94138 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2009-10-16 12:37
Making this a deferred blocker so as not to clutter 2.6.4 release.
msg96701 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2009-12-20 17:41
Many fixes of modules and packages outside Lib/test

Dev notes:
 * for bsddb and dbhash the warning message should include "module" to
be ignored by "test_support.import_module"
 * patch for mailbox is copied from Lib/cgi.py
 * other fixes are trivial
msg96704 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2009-12-20 17:48
Patch for the compiler package and astgen.py tool.

Basically:
  def __init__(self, (left, right), lineno=None):

==>

  def __init__(self, leftright, lineno=None):
msg96707 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2009-12-20 18:02
Patch for pprint: when keys are not the same type, "-3" emits warnings.

Partial backport from Py3k.
msg97221 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-04 18:14
In issue7092_lib_many_fixes.diff: why did you change some of the warning messages?

In issue7092_pprint.diff: I'm not sure these changes are right, because they could modify existing behaviour. Raymond, what do you think?
msg97228 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-04 22:32
Updated "lib_many_fixes" patch:
 * added filterwarning for pprint
 * added fixes for Lib/sunau.py and Lib/unittest/case.py

Ready for review and merge:
 * issue7092_lib_many_fixes_v2.diff
 * issue7092_compiler.diff
msg97229 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-04 22:38
One thing: "lambda k: k in selfdata" can be replaced with
"selfdata.__contains__". It may have better performance characteristics
too.
msg97231 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-04 22:53
I learned something.
msg97233 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-04 23:16
Looks good, thank you.
msg97234 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-04 23:23
Both patches have been committed in r77310.
msg97323 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-06 20:40
Still some "-3" warnings to silence:

./python -3m "collections" >/dev/null
./python -3c "import Cookie"
./python -3c "import idlelib.rpc"
./python -3c "import logging.handlers"
./python -3c "import multiprocessing"
./python -3c "import shelve"
./python -3c "import trace"

All these modules yield:
"DeprecationWarning: the cPickle module has been removed in Python 3.0"

There's also "bsddb" but it is deprecated.
msg97324 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-06 20:52
> All these modules yield:
> "DeprecationWarning: the cPickle module has been removed in Python 3.0"

I think this warning is both annoying (cPickle is a legitimate module to use in 2.x, since pickle is much slower) and useless (2to3 should be able to do the module rename -- Benjamin, does it?). Therefore I suggest to remove this warning.
msg97325 - (view) Author: Jean-Paul Calderone (exarkun) * (Python committer) Date: 2010-01-06 20:59
> I think this warning is both annoying (cPickle is a legitimate module to use in 2.x, since pickle is much slower) and useless (2to3 should be able to do the module rename -- Benjamin, does it?). Therefore I suggest to remove this warning.

You may be right, but keep in mind that cPickle and pickle are only *mostly* compatible with each other.  There are uses of one which will not automatically work if you switch to the other.
msg97327 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-06 21:03
+1 to remove this boring cPickle message.

cStringIO do not print such messages.
msg97356 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-01-07 14:40
>Antoine> (2to3 should be able to do the module rename -- Benjamin, does it?).
2to3 will rename cPickle to pickle.
msg97367 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-07 19:54
The Big Patch™.

It removes 99% of noisy deprecation messages.
msg97414 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-08 14:53
I split the Big Patch™ into pieces.
It should be easier to review and merge.

 - issue7092_syntax_imports.diff
   --> Only syntax and import_module(m, deprecated=True)

 - issue7092_check_warnings.diff
   --> Use test.test_support.check_warnings()

 - issue7092_filterwarnings.diff
   --> Use warnings.filterwarnings()

 - issue7092_json_sqlite.diff
   --> Silence external libraries

 - issue7092_cpickle.diff
   --> Remove cPickle warning

And there's a last patch for "test_index" attached to issue7532.


Then you reach the Zen of Python.
  “Do not speak — unless it improves on silence.”
msg97415 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-08 16:03
About issue7092_json_sqlite.diff: if json produces py3k warnings in normal use (does it?), the warnings should be suppressed in json itself, not in regrtest.py.
msg97418 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-08 17:17
Patch for JSON and SQLite libraries updated.
msg97434 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-01-08 19:23
issue7092_cpickle.diff was committed to trunk and 2.6.
msg97456 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2010-01-09 16:31
This can wait.
msg97497 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-01-10 04:13
Hello

I read the diff for revision 77310 and noticed that arguments with parens
(I mean things like ``def spam((x, y))``, forgot the name) were replaced
by grab-all arguments that are unpacked later (``def spam(x_y)``). I was
wondering whether the documentation for these changed functions was still
accurate when describing the arguments they take. It seems none of them
have a docstring, and docs.python.org/dev/ isn’t up to date so I can’t
check right now.

Kind regards
msg97499 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2010-01-10 04:52
The documentation is still accurate. The translation is literal so there no
shift except where the unpacking exception occurs.

On Sat, Jan 9, 2010 at 20:13, Éric Araujo <report@bugs.python.org> wrote:

>
> Éric Araujo <merwok@netwok.org> added the comment:
>
> Hello
>
> I read the diff for revision 77310 and noticed that arguments with parens
> (I mean things like ``def spam((x, y))``, forgot the name) were replaced
> by grab-all arguments that are unpacked later (``def spam(x_y)``). I was
> wondering whether the documentation for these changed functions was still
> accurate when describing the arguments they take. It seems none of them
> have a docstring, and docs.python.org/dev/ isn’t up to date so I can’t
> check right now.
>
> Kind regards
>
> ----------
> nosy: +Merwok
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue7092>
> _______________________________________
>
msg97944 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-17 13:49
I've created issue7723 for sqlite3 module using buffer().
It's not so simple.
msg97950 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-17 15:08
Patches updated against trunk.
msg97951 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-17 15:28
Re-uploaded "syntax_imports_v2" with patch for test_bsddb.py
msg98254 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-24 22:24
Re-uploaded after fixes for #7737.

To remove all "-3" warnings:
 - apply the 4 patches
 - fix SQLite "buffer()" warnings (issue #7223)
msg98341 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-01-26 15:59
json is now fixed in r77755.
msg98491 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2010-01-29 00:34
Here is my review of issue7092_syntax_imports_v3.diff:

- test_itertools.py: please replace
      [tuple([arg[i] if i < len(arg) else None for arg in args])
       for i in range(max(map(len, args)))]
  by something more readable (nested for loops for example)

- test_mailbox.py: why doesn't test_support.import_module('rfc822')
  specify deprecated=True? maybe the module can be imported normally...

- test_pyclbr.py:   replace self.assertTrue(key in obj) with assertIn()
- test_wsgiref.py:  replace self.assertTrue(key in h.environ)

- test_queue.py: test could be identical to the one in py3k.
msg98494 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-01-29 01:28
Here's mine about issue7092_check_warnings_v3.diff:

1) test_callable should keep testing callable() and the warnings should be caught;
2) in test_bsddb3 the problems should be correct in the module if possible and worth it (the module is deprecated);
3) next to the several '# Silence py3k warnings' it would be nice to have a note about what warning you are exactly silencing;
4) def test_deprecated_builtin_map -> test_deprecated_builtin_map_with_None, otherwise it seems that map is deprecated;
5) in test[_deep]_copy I'm not entirely sure that the tests are equivalent using in (and if they are you should use assertIn);
6) in test_socket I would keep callable, also shouldn't the raise in the next line raise a warning as well?;
7)  the self.assertEqual(`u2`, `d2`) in test_userdict could just use repr() instead;
8) a few tests in test_weakref should use assert[Not]In instead of assertTrue(x [not] in y).
msg98507 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-01-29 12:21
A couple of comments about issue7092_syntax_imports_v3.diff too:
1) in test_copy you remove (k,v), but left the name 'k' even if now it represent the item and not the key;
2) in test_fractions you should probably use self.fail() instead of an assert;
3) on test_ftp you can use two separate lines and remove the ';';
4) in test_pyclbr there's one extra 'f' in the comment in assertHaskey;
5) in test_xml_etree_c you can either leave callable() and catch the warning or use isinstance(x, collections.Callable) instead (there are also a few more places where callable was used too).
msg98528 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-29 19:15
Thank you for the review and your comments.
Here, the replies.


>
> Amaury review - msg98491
>
> Here is my review of issue7092_syntax_imports_v3.diff:
>
> - test_itertools.py: please replace
>       [tuple([arg[i] if i < len(arg) else None for arg in args])
>        for i in range(max(map(len, args)))]
>   by something more readable (nested for loops for example)

It is the 3.x syntax.
--> No change

> - test_mailbox.py: why doesn't test_support.import_module('rfc822')
>   specify deprecated=True? maybe the module can be imported normally...

Added the "deprecated=True"

> - test_pyclbr.py:   replace self.assertTrue(key in obj) with assertIn()
> - test_wsgiref.py:  replace self.assertTrue(key in h.environ)
> - test_queue.py: test could be identical to the one in py3k.

Thanks
--> Done

> 
> Ezio review - msg98494
> 
> Here's mine about issue7092_check_warnings_v3.diff:
> 
> 1) test_callable should keep testing callable() and the warnings should be caught;

Done

> 2) in test_bsddb3 the problems should be correct in the module if possible and worth it (the module is deprecated);

Ok. I prepare a separate patch to fix bsddb3

> 3) next to the several '# Silence py3k warnings' it would be nice to have a note about what warning you are exactly silencing;
> 4) def test_deprecated_builtin_map -> test_deprecated_builtin_map_with_None, otherwise it seems that map is deprecated;

Done

> 5) in test[_deep]_copy I'm not entirely sure that the tests are equivalent using in (and if they are you should use assertIn);

Will use assertSetEqual, no need to reinvent the wheel

> 6) in test_socket I would keep callable, also shouldn't the raise in the next line raise a warning as well?;

Ok to keep callable. For the next line, I do not see the warning.

> 7)  the self.assertEqual(`u2`, `d2`) in test_userdict could just use repr() instead;

Done

> 8) a few tests in test_weakref should use assert[Not]In instead of assertTrue(x [not] in y).

Done

> 
> Ezio review - msg98507
> 
> A couple of comments about issue7092_syntax_imports_v3.diff too:
> 1) in test_copy you remove (k,v), but left the name 'k' even if now it represent the item and not the key;

Changed 'k'-> 'pair' (like 3.x)

> 2) in test_fractions you should probably use self.fail() instead of an assert;

The surrounding methods use "assert "
--> No change

> 3) on test_ftp you can use two separate lines and remove the ';';

Done

> 4) in test_pyclbr there's one extra 'f' in the comment in assertHaskey;

It is not an extra f. 'iff' = "if and only if" (not obvious for non-English people)

> 5) in test_xml_etree_c you can either leave callable() and catch the warning or use isinstance(x, collections.Callable) instead (there are also a few more places where callable was used too).

It is done this way in 3.x.
I propose to fix it separately (if a fix is required).



Now I prepare the updated patches.
I follow the proposal of Amaury: create a specific "test_support.silence_py3k_warnings()" context manager.
It replaces the "check_warnings" and "filterwarnings" of the proposed patches.
msg98543 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-29 23:22
Each patch can be reviewed and committed separately (except the last 2).

[patch 1] bsddb3.diff – related to Bsddb3
[patch 2] test_support.diff – new helper "silence_py3k_warnings()"
[patch 3] test_exceptions.diff – "test_pep352" and "test_exceptions"
[patch 4] Wd_warnings.diff – fix few "-Wd" warnings
[patch 5] syntax_fixes.diff – fix syntax only (2to3-like)
[patch 6] silence_imports.diff – import deprecated modukes


Patches below require the new helper "silence_py3k_warnings" (patch 2)

[patch 7] py3k_warnings_args.diff – 26 files
[patch 8] py3k_warnings_noargs.diff – 28 files
msg98554 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-01-30 07:26
Warnings for imports of deprecated modules are now silenced in r77841 (patch 6 / silence_imports.diff).
msg98557 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-01-30 10:06
Cleanup test_exceptions:
 - removed "filterwarnings" for "testSlicing"
msg98597 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-01-31 03:15
The patch for bsddb3 looks good, however there's no reason (IMHO) to keep in the tests those "if sys.version_info[0] < 3:" or replace the version with (2,6) since we are already using things like assertIn that are 2.7-only. I changed it only to avoid warnings, and left it unchanged in other places (not related to this issue) and in dbtables.py (to preserve compatibility in the unlikely case that someone wants to try running 2.7's bsddb with older versions of Python).
Attached a new patch.
msg98723 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-02-02 09:06
bsddb is now fixed in r77910.
msg98724 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-02 09:19
Proposed patch to filter out some deprecated comparisons in "unittest" module.
msg98750 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-02-02 17:35
test_exceptions and test_pep352 fixed in r77913.
msg98751 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-02 17:45
test_unittest fixed in r77911. See also #7837.
msg98752 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-02-02 17:55
In issue7092_test_support:
1) silence_py3k_warning should have a docstring that explain what the function does and what filters should be, possibly including an example;
2) I'd use "if not filters:" instead of "if filters == ():";
3) are there cases where the third arg of filterwarnings is not DeprecationWarning? If not, it's probably better to turn "filters" in a list of regex instead than a sequence of tuples like (regex, DeprecationWarning);
4) maybe silence_py3k_warning could yield an instance of WarningsRecorder, in case someone wants to access the silenced warnings.
msg98762 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-02 22:45
Docstring added.

Notes:
 - there's 2 categories of -3 warnings: SyntaxWarning and DeprecationWarning.
 - AFAICT, the WarningsRecorder needs "catch_warnings(record=True)".
   And in such case, *all* warnings are silenced.
msg98773 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-02-03 06:21
Applied the syntax fixes in r77942.
msg98804 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-04 00:28
The enhancement proposed on #7849 should be considered before reviewing the last 2 patches.

If #7849 is accepted, these patches will need update.
msg100702 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-03-09 07:08
Silence the last warnings, using check_py3k_warnings.

But we could provide a smaller patch, if #7832 is fixed before.
msg101138 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2010-03-16 00:00
Checking the pybsddb 4.8.4devel with current trunk I still see this:

"""
Berkeley DB 4.8.26: (December 18, 2009)
bsddb.db.version():   (4, 8, 26)
bsddb.db.__version__: 4.8.4devel1
bsddb.db.cvsid:       $Id: _bsddb.c,v 6408a812f035 2010/03/15 19:15:06 jcea $
py module:            /home/pybsddb/build/lib.solaris-2.10-i86pc-2.7/bsddb3/__init__.pyc
extension module:     /home/pybsddb/build/lib.solaris-2.10-i86pc-2.7/bsddb3/__init__.pyc
python version:       2.7a4+ (trunk, Mar 16 2010, 00:50:35) 
[GCC 4.4.3]
My pid:               5068
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
............................................................................................................................................................................................................................................................................................................................................................................................................................................./usr/local/lib/python2.7/threading.py:575: DeprecationWarning: sys.exc_clear() not supported in 3.x; use except clauses
  self.__exc_clear()
.........................................
----------------------------------------------------------------------
Ran 470 tests in 7.605s

OK

"""

Python 2.6.4 has the same issue too.
msg101220 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-03-17 12:28
> Checking the pybsddb 4.8.4devel with current trunk I still see this:

It is because the "test_early_close" module calls resetwarnings().
It defeats the filter in the "threading" module.

You may change the test case with a context manager:

  with warnings.catch_warnings():
      warnings.resetwarnings()
      # test the warning
msg101223 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-03-17 13:54
I took part of Florent latest patch, changed a few things and committed it in r79023.
msg101280 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2010-03-18 20:38
Florent you are right, good catch. I can not use context managers because "with" is invalid syntax in python 2.3 and 2.4, that I must support for a while.

I have implemented a context manager manually, following the description in PEP 343. This change is available in pybsddb 4.8.3+. I plan to integrate pybsddb 4.8.3+, see issue8156.
msg101411 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-03-21 01:26
More warnings silenced with r79165.
msg101418 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-03-21 11:15
other py3k warnings silenced with r79187 r79188 r79189
msg102045 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-03-31 23:26
Now the "-Wd" and "-3" flags are active on some buildbots.
And the first failures ...


Need to backport fixes from py3k branch for:
- cgitb "SyntaxWarning: tuple parameter unpacking has been removed in 3.x"
- idlelib "reduce() not supported in 3.x; use functools.reduce()"


And test_multiprocessing is failing on: "sys.exc_clear() not supported in 3.x; use except clauses"
msg102074 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-04-01 08:18
Other py3k warnings:

lib\distutils\util.py:209: DeprecationWarning: apply() not supported in 3.x; use func(*args, **kwargs)
  return apply(os.path.join, paths)

lib\distutils\command\build_ext.py:679: DeprecationWarning: apply() not supported in 3.x; use func(*args, **kwargs)
  return apply(os.path.join, ext_path) + '_d' + so_ext

lib\platform.py:1035: DeprecationWarning: dict.has_key() not supported in 3.x; use the in operator
  if _default_architecture.has_key(sys.platform):
msg102119 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-04-01 18:18
Fixed with r79558, except test_multiprocessing.
msg102150 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-04-02 09:17
Additional fixes: r79576, r79577, r79578 (idlelib package and some test modules)
msg112146 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-07-31 12:06
This issue is over, except for #7723 which is tracked separately.
msg112243 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-08-01 01:02
Barry, is it OK if I backport this to 2.6 before the rc1?
msg112607 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2010-08-03 13:59
Hi Ezio, what's the status on this issue for 2.6.6rc1?
msg112677 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2010-08-03 20:56
I am removing this as a release blocker given all of Ezio's great work to get the test suite clean with -3.  I will leave it up to him to actually close the issue once the work is complete.  It no longer needs to block 2.6.6.
msg112686 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2010-08-03 21:16
I fixed the deprecation warnings on 2.6 in r83519, r83576-r83579, r83620-r83622, r83627-r83632, r83635, r83637-83642, r83652-83656, r83658, r83687.
Now the test suite should pass with and without -3 -Wd with no errors and no warnings (except an import warning on _ctypes and/or _multiprocessing).
This can be closed.
History
Date User Action Args
2022-04-11 14:56:53adminsetgithub: 51341
2010-08-03 21:16:14ezio.melottisetstatus: open -> closed

messages: + msg112686
2010-08-03 20:56:42barrysetpriority: release blocker -> high

messages: + msg112677
2010-08-03 13:59:44barrysetmessages: + msg112607
2010-08-01 23:13:39ezio.melottisetpriority: critical -> release blocker
2010-08-01 01:02:16ezio.melottisetstatus: closed -> open

messages: + msg112243
versions: + Python 2.6
2010-07-31 12:06:36floxsetstatus: open -> closed
messages: + msg112146

dependencies: - sqlite only accept buffer() for BLOB objects (input/output)
resolution: accepted -> fixed
stage: patch review -> resolved
2010-04-03 15:27:35benjamin.petersonsetpriority: release blocker -> critical
2010-04-02 09:17:32floxsetmessages: + msg102150
2010-04-01 18:18:55floxsetmessages: + msg102119
2010-04-01 11:16:53floxlinkissue4577 superseder
2010-04-01 08:18:19floxsetmessages: + msg102074
2010-03-31 23:26:55floxsetmessages: + msg102045
2010-03-21 11:15:40floxsetmessages: + msg101418
2010-03-21 01:26:18floxsetmessages: + msg101411
2010-03-18 20:38:15jceasetmessages: + msg101280
2010-03-18 20:38:01jceasetmessages: - msg101279
2010-03-18 20:37:26jceasetmessages: + msg101279
2010-03-17 13:54:32ezio.melottisetmessages: + msg101223
2010-03-17 12:28:26floxsetmessages: + msg101220
2010-03-16 00:00:12jceasetnosy: + jcea
messages: + msg101138
2010-03-09 20:09:40floxunlinkissue7772 dependencies
2010-03-09 07:08:29floxsetfiles: + issue7092_without_7832.diff

dependencies: + assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
messages: + msg100702
2010-03-09 07:01:51floxsetfiles: - issue7092_test_support_v2.diff
2010-03-09 07:01:45floxsetfiles: - issue7092_py3k_warnings_noargs_v2.diff
2010-03-09 07:01:40floxsetfiles: - issue7092_py3k_warnings_args_v2.diff
2010-02-04 00:28:19floxsetmessages: + msg98804
2010-02-03 20:09:42floxsetdependencies: + Improve "test_support.check_warnings()"
2010-02-03 06:22:23ezio.melottisetfiles: - issue7092_syntax_fixes.diff
2010-02-03 06:21:52ezio.melottisetassignee: ezio.melotti
messages: + msg98773
2010-02-02 22:45:41floxsetfiles: + issue7092_test_support_v2.diff

messages: + msg98762
2010-02-02 22:20:01floxsetfiles: - issue7092_test_support.py
2010-02-02 17:55:22ezio.melottisetmessages: + msg98752
2010-02-02 17:45:25floxsetmessages: + msg98751
2010-02-02 17:44:42floxsetfiles: - issue7092_unittest.py
2010-02-02 17:35:50ezio.melottisetfiles: - issue7092_test_exceptions_v2.diff
2010-02-02 17:35:34ezio.melottisetmessages: + msg98750
2010-02-02 09:19:18floxsetfiles: + issue7092_unittest.py

messages: + msg98724
2010-02-02 09:06:06ezio.melottisetmessages: + msg98723
2010-02-02 09:04:20floxsetfiles: - issue7092_bsddb3v2.diff
2010-02-02 09:04:16floxsetfiles: - issue7092_bsddb3.diff
2010-02-01 00:09:13floxsetfiles: + issue7092_py3k_warnings_noargs_v2.diff
2010-02-01 00:08:42floxsetfiles: + issue7092_py3k_warnings_args_v2.diff
2010-02-01 00:08:04floxsetfiles: - issue7092_py3k_warnings_noargs.diff
2010-02-01 00:07:59floxsetfiles: - issue7092_py3k_warnings_args.diff
2010-02-01 00:01:49floxsetfiles: - issue7092_Wd_warnings.diff
2010-01-31 03:15:39ezio.melottisetfiles: + issue7092_bsddb3v2.diff

messages: + msg98597
2010-01-30 10:21:49floxsetfiles: - issue7092_silence_imports.diff
2010-01-30 10:07:08floxsetfiles: + issue7092_test_exceptions_v2.diff

messages: + msg98557
2010-01-30 10:03:37floxsetfiles: - issue7092_test_exceptions.diff
2010-01-30 07:26:10ezio.melottisetmessages: + msg98554
2010-01-29 23:22:03floxsetmessages: + msg98543
2010-01-29 23:10:17floxsetfiles: + issue7092_py3k_warnings_noargs.diff
2010-01-29 23:09:44floxsetfiles: + issue7092_py3k_warnings_args.diff
2010-01-29 23:04:18floxsetfiles: + issue7092_silence_imports.diff
2010-01-29 21:28:33exarkunsetnosy: - exarkun
2010-01-29 21:14:51floxsetfiles: + issue7092_syntax_fixes.diff
2010-01-29 21:13:00floxsetfiles: + issue7092_Wd_warnings.diff
2010-01-29 21:12:13floxsetfiles: + issue7092_test_exceptions.diff
2010-01-29 21:07:48floxsetfiles: - issue7092_filterwarnings_v3.diff
2010-01-29 21:07:44floxsetfiles: - issue7092_check_warnings_v3.diff
2010-01-29 21:07:39floxsetfiles: - issue7092_syntax_imports_v3.diff
2010-01-29 20:11:45floxsetfiles: - issue7092_json.diff
2010-01-29 20:10:53floxsetfiles: + issue7092_test_support.py
2010-01-29 19:24:40floxsetfiles: + issue7092_bsddb3.diff
2010-01-29 19:24:21floxsetfiles: - issue7269_bsddb3.diff
2010-01-29 19:24:08floxsetfiles: + issue7269_bsddb3.diff
2010-01-29 19:15:39floxsetmessages: + msg98528
2010-01-29 12:21:34ezio.melottisetmessages: + msg98507
2010-01-29 01:28:51ezio.melottisetmessages: + msg98494
2010-01-29 00:34:21amaury.forgeotdarcsetnosy: + amaury.forgeotdarc
messages: + msg98491
2010-01-26 15:59:34ezio.melottisetmessages: + msg98341
2010-01-24 22:24:29floxsetfiles: + issue7092_filterwarnings_v3.diff

messages: + msg98254
stage: resolved -> patch review
2010-01-24 22:17:57floxsetfiles: + issue7092_check_warnings_v3.diff
2010-01-24 22:16:59floxsetfiles: + issue7092_syntax_imports_v3.diff
2010-01-24 22:15:38floxsetfiles: - issue7092_check_warnings.diff
2010-01-24 22:15:30floxsetfiles: - issue7092_syntax_imports_v2.diff
2010-01-24 22:15:26floxsetfiles: - issue7092_filterwarnings_v2.diff
2010-01-24 18:51:10floxlinkissue7772 dependencies
2010-01-17 19:54:13brett.cannonsetnosy: - brett.cannon
2010-01-17 15:28:56floxsetfiles: + issue7092_syntax_imports_v2.diff

messages: + msg97951
2010-01-17 15:27:54floxsetfiles: - issue7092_syntax_imports_v2.diff
2010-01-17 15:09:34floxsetfiles: + issue7092_filterwarnings_v2.diff
2010-01-17 15:09:05floxsetfiles: + issue7092_syntax_imports_v2.diff

messages: + msg97950
2010-01-17 15:07:45floxsetfiles: - issue7092_filterwarnings.diff
2010-01-17 15:07:40floxsetfiles: - issue7092_syntax_imports.diff
2010-01-17 13:54:51floxsetfiles: + issue7092_json.diff
2010-01-17 13:51:49floxsetfiles: - issue7092_json_sqlite_v2.diff
2010-01-17 13:49:06floxsetdependencies: + sqlite only accept buffer() for BLOB objects (input/output)
messages: + msg97944
2010-01-12 15:33:56floxsetfiles: - unnamed
2010-01-10 04:52:52brett.cannonsetfiles: + unnamed

messages: + msg97499
2010-01-10 04:13:32eric.araujosetnosy: + eric.araujo
messages: + msg97497
2010-01-09 20:09:20benjamin.petersonsetpriority: deferred blocker -> release blocker
2010-01-09 16:31:07benjamin.petersonsetpriority: release blocker -> deferred blocker

messages: + msg97456
2010-01-08 19:41:08pitrousetfiles: - issue7092_regrtest_clean.diff
2010-01-08 19:30:14pitrousetfiles: - issue7092_cpickle.diff
2010-01-08 19:23:29pitrousetmessages: + msg97434
2010-01-08 17:17:50floxsetfiles: + issue7092_json_sqlite_v2.diff

messages: + msg97418
2010-01-08 17:16:37floxsetfiles: + issue7092_regrtest_clean.diff
2010-01-08 17:16:18floxsetfiles: - issue7092_json_sqlite.diff
2010-01-08 16:03:52pitrousetmessages: + msg97415
2010-01-08 14:53:42floxsetfiles: + issue7092_json_sqlite.diff

messages: + msg97414
2010-01-08 14:53:01floxsetfiles: + issue7092_filterwarnings.diff
2010-01-08 14:52:39floxsetfiles: + issue7092_check_warnings.diff
2010-01-08 14:51:52floxsetfiles: + issue7092_syntax_imports.diff
2010-01-08 09:06:10floxsetfiles: - issue7092_Lib_tests_big_patch.diff
2010-01-07 19:54:56floxsetfiles: + issue7092_Lib_tests_big_patch.diff

messages: + msg97367
2010-01-07 17:44:10floxsetfiles: - issue7092_compiler.diff
2010-01-07 17:44:04floxsetfiles: - issue7092_lib_many_fixes_v3.diff
2010-01-07 17:43:54floxsetfiles: + issue7092_cpickle.diff
2010-01-07 14:40:44brian.curtinsetnosy: + brian.curtin
messages: + msg97356
2010-01-06 21:03:24floxsetmessages: + msg97327
2010-01-06 20:59:18exarkunsetmessages: + msg97325
2010-01-06 20:52:15pitrousetmessages: + msg97324
2010-01-06 20:40:20floxsetstatus: pending -> open

messages: + msg97323
2010-01-04 23:23:38pitrousetstatus: open -> pending

messages: + msg97234
stage: commit review -> resolved
2010-01-04 23:16:19pitrousetresolution: accepted
messages: + msg97233
stage: commit review
2010-01-04 22:53:14floxsetfiles: + issue7092_lib_many_fixes_v3.diff

messages: + msg97231
2010-01-04 22:52:49floxsetfiles: - issue7092_lib_many_fixes_v2.diff
2010-01-04 22:38:42pitrousetmessages: + msg97229
2010-01-04 22:34:23floxsetfiles: - issue7092_pprint.diff
2010-01-04 22:33:08floxsetfiles: - issue7092_lib_many_fixes.diff
2010-01-04 22:33:00floxsetfiles: + issue7092_lib_many_fixes_v2.diff

messages: + msg97228
2010-01-04 18:14:16pitrousetnosy: + rhettinger
messages: + msg97221
2010-01-04 17:03:54pitrousetpriority: deferred blocker -> release blocker
2009-12-20 18:02:32floxsetfiles: + issue7092_pprint.diff

messages: + msg96707
2009-12-20 17:48:59floxsetfiles: + issue7092_compiler.diff

messages: + msg96704
2009-12-20 17:41:38floxsetfiles: + issue7092_lib_many_fixes.diff
keywords: + patch
messages: + msg96701
2009-12-15 17:13:38floxsetnosy: + flox
2009-10-18 00:29:08esamsetnosy: + esam
2009-10-16 12:37:06barrysetpriority: release blocker -> deferred blocker
nosy: + barry
messages: + msg94138

2009-10-14 19:21:28pitrousetmessages: + msg94016
2009-10-14 19:20:48pitrousetfiles: + stderr.log

messages: + msg94015
2009-10-14 19:14:10pitrousetmessages: + msg94012
2009-10-11 15:48:50ezio.melottisetnosy: + ezio.melotti
2009-10-09 18:29:09pitrousetnosy: + pitrou
messages: + msg93806
2009-10-09 18:21:07brett.cannonsetpriority: release blocker
nosy: + brett.cannon
messages: + msg93805

2009-10-09 15:15:09benjamin.petersonsetnosy: + benjamin.peterson
messages: + msg93800
2009-10-09 14:30:32exarkuncreate