[issue6288] Update contextlib.nested docs in light of deprecation
Hagen Fürstenau hfuerste...@gmx.net added the comment: Does that mean that nested() can be removed or changed incompatibly in 3.2 at the same time that an alternative way for handling the remaining use case is introduced? This would seem to violate the promise in PEP 5, that users will have at least a year to test their programs and migrate them from use of the deprecated construct to the alternative one. -- nosy: +hagen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6287] distutils.core.setup does not document the 'license' meta-data
Tarek Ziadé ziade.ta...@gmail.com added the comment: done in r73441 and merged in all branches. Thanks ! -- components: +Documentation status: open - closed versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6287 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6164] [AIX] Patch to correct the AIX C/C++ linker argument used for 'runtime_library_dirs'
Tarek Ziadé ziade.ta...@gmail.com added the comment: This patch will not work with the compiler is gcc or g++ Is that intended ? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6164 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6291] TypeError: b2a_base64() argument 1 must be bytes or buffer, not str during SMTP.login
New submission from Milivoj Milani miliv...@gzr.hr: When trying to send an e-mail using a tutorial like example, I get the following message: Traceback (most recent call last): File test.py, line 3, in module server.login(domena\someuser,somepassword) File C:\Python\lib\smtplib.py, line 583, in login %s %s % (AUTH_LOGIN, encode_base64(user))) File C:\Python\lib\email\base64mime.py, line 96, in body_encode enc = b2a_base64(s[i:i + max_unencoded]).decode(ascii) TypeError: b2a_base64() argument 1 must be bytes or buffer, not str -- components: Library (Lib) files: test.py messages: 89428 nosy: milivojm severity: normal status: open title: TypeError: b2a_base64() argument 1 must be bytes or buffer, not str during SMTP.login type: behavior versions: Python 3.0 Added file: http://bugs.python.org/file14307/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6284] C/API PyErr_AsUnicode()
Campbell Barton ideasma...@gmail.com added the comment: Thanks for the feedback, I wasnt aware of PyErr_Display, its not documented as far as I know. http://docs.python.org/dev/py3k/genindex-all.html For blender, its development id still in progress so we don't yet have an internal console replacement. however we use a number of python apis in blender (game engine api, UI api, wrapping our own data) - So there are a number of places where this function could come in handy, and completely replacing the stdout isn't always an option - when running the game engine for instance. Ill look into using a PyErr_DisplayEx -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6284 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6284] C/API PyErr_AsUnicode()
Campbell Barton ideasma...@gmail.com added the comment: Updated with an PyErr_DisplayEx function that accepts a file argument. -- Added file: http://bugs.python.org/file14308/PyErr_AsUnicode_r73443.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6284 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6291] TypeError: b2a_base64() argument 1 must be bytes or buffer, not str during SMTP.login
R. David Murray rdmur...@bitdance.com added the comment: This is a duplicate of issue 5259, and has already been fixed. Thanks for the report. -- nosy: +r.david.murray priority: - normal resolution: - duplicate stage: - committed/rejected status: open - closed superseder: - smtplib is broken in Python3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6288] Update contextlib.nested docs in light of deprecation
Nick Coghlan ncogh...@gmail.com added the comment: That's a good point actually - with 3.1's in-between status and the lack of deprecation in 2.6, nested() is going to have to stick around for 2.7/3.2 anyway. So PendingDeprecation now with full deprecation in 2.7/3.2 when we will hopefully have a better alternative in place is probably the way to go. Updating the docs to cover only the recommended use case is still something I want to do this week though (hopefully tomorrow). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1191964] asynchronous Subprocess
R. David Murray rdmur...@bitdance.com added the comment: Retargeting to 3.2 since 3.1 is now feature-frozen. -- nosy: +r.david.murray versions: +Python 3.2 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1191964 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6292] Fix tests to work with -OO
New submission from Collin Winter coll...@gmail.com: The attached patch fixes a number of tests to work when -OO is given to Python. The majority of these tests are docstring-related, either doctests or making assertions about __doc__, with a handful of tests testing that assert statements will trigger and another handful of distutils tests that are looking for .pyc files. With this applied, PYTHONOPTIMIZE=2 ./python.exe -OO Lib/test/regrtest.py now passes for trunk. -- components: Tests files: oo_tests.patch keywords: easy, patch messages: 89434 nosy: collinwinter, jyasskin, rnk severity: normal stage: patch review status: open title: Fix tests to work with -OO type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file14309/oo_tests.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6292 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6288] Update contextlib.nested docs in light of deprecation
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: There is *no* reason to downgrade the warning. We can leave it as deprecated in 3.1 and remove it in 3.3 if we want. A PendingDeprecationWarning is just a plain bad idea, it doesn't actually warn the users. We introduced that construct in Python 2.3 to be used *rarely* for deeply entrenched things like string exceptions that would be eventually removed. For the most part, everything else gets deprecated directly. Also, remember that this construct is not being deprecated just because it is duplicative; it is being deprecated because it is a bug factory when used as advertised -- it is a harmful construct -- it *needs* a warning. Someone like Hagan, using it for a corner case, can easily put a copy and paste version in their own code and use it forever. There are likely very few such users now (but there will be more if we fail to provide a real warning). -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6293] Have regrtest.py echo back sys.flags
New submission from Collin Winter coll...@gmail.com: This patch makes regrtest.py echo back the contents of sys.flags at the beginning of a test run. Unladen Swallow has found this useful for verifying that the regrtest.py settings in the Makefile and in our Buildbot configs are interacting as expected. Example output: $ PYTHONOPTIMIZE=2 ./python.exe -OO Lib/test/regrtest.py Testing with flags: sys.flags(debug=0, py3k_warning=0, division_warning=0, division_new=0, inspect=0, interactive=0, optimize=2, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, tabcheck=0, verbose=0, unicode=0, bytes_warning=0) test_grammar test_opcodes test_dict test_builtin test_exceptions test_types [snip] $ -- components: Tests files: regrtest_flags.patch keywords: easy, patch messages: 89436 nosy: collinwinter severity: normal stage: patch review status: open title: Have regrtest.py echo back sys.flags type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file14310/regrtest_flags.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6293 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6288] Update contextlib.nested docs in light of deprecation
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: To be clear, I'm strongly -1 on switching to a PendingDeprecationWarning. That is not what it is for. There is nothing in the PEP 5 language that requires it (a PDW isn't even mentioned, the pep is mainly targeted at deep language changes to the parser and compiler). I realize that Hagan wants to resurrect this construct, but he needs to recognize that it is unsalvagable. It is likely that most current uses of nested() are replaceable by the new with-statement. Some of those uses are buggy (no clean-up for failed constructors). The process of converting those cases will fix the bugs. We are doing these users a disservice if the warning is made silent by default. People *need* to be notified about the potential bugginess. Essentially, the new with-statement syntax is a bugfix (the old API was hopelessly error-prone in a way that is hard to find and fix). The statement in the docs that nested() is *equivalent* to two nested withs is erroneous -- the function is buggy because the equivalence is broken (a user is much better-off just writing two with-statements than using nested()). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6164] [AIX] Patch to correct the AIX C/C++ linker argument used for 'runtime_library_dirs'
Trent Mick tre...@gmail.com added the comment: Tarek, This should not affect anyone using gcc or g++ on AIX because of this check just before the lines added by this patch: elif compiler[:3] == gcc or compiler[:3] == g++: return -Wl,-R + dir The intention of the patch is to fix linker argument handling with NOT using gcc, i.e. when using IBM's native AIX compiler. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6164 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6292] Fix tests to work with -OO
Antoine Pitrou pit...@free.fr added the comment: Rather than silently skipping stuff or writing to stderr, the patch should, as much as possible, use the new test-skipping API in unittest. Perhaps DocTestSuite could centralize some of the effort by inspecting sys.flags and skipping accordingly (but users may also set __doc__ manually). -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6292 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6215] Backport the IO lib to trunk
Antoine Pitrou pit...@free.fr added the comment: Well, the patch looks ok, so you can commit it if it fixes things on Windows. (I honestly haven't tested it, though) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6294] Improve shutdown exception ignored message
New submission from Terry J. Reedy tjre...@udel.edu: When (at least sometimes) exceptions occur during shutdown, warnings like the following appear: Exception TypeError: 'NoneType' object is not callable in ignored This is apparently meant to be read as Exception TypeError: 'NoneType' object is not callable in ... [was] ignored instead of, for instance Exception TypeError: 'NoneType' object is not callable in ignored Even when parsed correctly, it is a bit mysterious (who/what ignored the exception?) to one not in the know and has generated more than one python-list thread. Suggestion (from John Machin): reword to something like Shutdown ignored this exception: TypeError: 'NoneType' object is not callable This would tell people that they might need to find out more about the shutdown process. Would it be permissible to change this in 3.1? -- keywords: easy messages: 89441 nosy: tjreedy severity: normal status: open title: Improve shutdown exception ignored message type: feature request versions: Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6294 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6294] Improve shutdown exception ignored message
R. David Murray rdmur...@bitdance.com added the comment: Since 3.1 is in final release candidate, a change like this is not appropriate for 3.1. This error message is generated in PyErr_WriteUnraisable, which is called from many contexts, including __del__ methods. A __del__ method called during shutdown is most likely what is generating the error you are speaking of, but as far as I know the __del__ method has no way to know that it is being called during shutdown in particular. So the proposed fix to the message won't work. The reason this message is so mysterious is that in this particular case there is additional information that normally appears in the message that has apparently also been nullified during shutdown and that token is simply omitted. This appears to be a bug, since the code substitutes unknown for other elements that are substituted into the message if they are NULL, but does not do so for the object passed in to the subroutine. Either the fact that the object prints as the empty string is a bug, or unknown should be substituted for it. With that bug fixed, the message would read: Exception TypeError: 'NoneType' object is not callable in unknown ignored which is more easily parsed correctly. As long as we're mucking about in that code, though, perhaps a more generic reformatting of the message would be clearer even with that bug fixed. I suggest: The following Exception of type TypeError was raised in unknown but was ignored: 'NoneType' object is not callable -- components: +Interpreter Core nosy: +r.david.murray priority: - low stage: - test needed type: feature request - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6294 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2622] Import errors in email.message.py
John Jackson johnjack...@pobox.com added the comment: Also occurs in 2.6... -- versions: +Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2622 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
