[issue10141] SocketCan support
Charles-François Natali added the comment: Are you saying that an additional clause for CAN_RAW being defined should be added around where it is used? Would that sort things out? Yes. I'd rather not just revert my change, as that would mean I couldn't compile the SSL module. I don't get it: how could the previous code prevent the SSL module from being built? What error were you getting? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10141 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20999] setlocale, getlocale succession -- ValueError or (None, None)
Ned Deily added the comment: It's hard to be absolutely sure what is going on here since you show several different interpreters and appear to be running on a non-standard, unsupported platform but, as David noted, the primary issue is that the process locale has almost certainly not been set to a correct value. In general, OS X does not set a default locale for a login process, although programs like Terminal.app may do so by default when they start a login shell for you. But if you login via ssh, for example, no locale environment variable will be set unless you do it yourself. You can examine the environment variables in the running interpreter with: import os,pprint pprint.pprint(dict(os.environ)) [...] 'LANG': 'en_US.UTF-8', [...] Look for LANG or LC_ALL variables. You can also use locale.getdefaultlocale() to see what the locale module is using as a default. You can override or establish a default by setting the LANG environment variable in your shell session; to do it permanently, add the setting to your login shell's startup profile. For example: export LANG=en_US.UTF-8 The secondary issue is the segfault. You say you are running on Mountain Lion 10.9.1 but OS X Mountain Lion is 10.8.x. If you are, in fact, running on 10.9.1 (also known an Mavericks) with the python.org 3.3.2, the segfault using the interactive interpreter is the problem documented in Issue18458 and has nothing to do with locale. The solution for that is to upgrade to a more recent Python 3, either Python 3.3.5 or the newly-released 3.4.0. -- nosy: +ned.deily resolution: - works for me stage: - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20999 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21000] json.tool ought to have a help flag
Changes by Berker Peksag berker.pek...@gmail.com: -- nosy: +berker.peksag ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21000 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20844] coding bug remains in 3.3.5rc2
Marc Schlaich added the comment: I can reproduce this one. There are a few conditions which needs to be met: - Linux line endings - File needs to have at least x lines (empty lines are fine). I guess this is the point why no one could reproduce it. The attached file has 19 lines but probably no one copy/pasted the empty lines. Downloading the file reproduces this in my case. The length of the encoding declaration is relevant to the number of required newlines. `#coding:latin-1` fails at a file with 19 lines, `#coding: latin-1` (whitespace added) requires 20 lines. More observations: - Also reproducible if utf8 is used as alias for utf-8 (`#coding: utf8` + 17 lines), but not reproducible with utf-8 - Python 3.4 is affected, too - No issues on Python 3.3.2 -- nosy: +schlamar versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20844 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20999] setlocale, getlocale succession -- ValueError or (None, None)
Ronald Oussoren added the comment: The locale issue is that on a default (us english) install of 10.9 the following locale related environment variables are set: $ set | grep UTF LANG=en_US.UTF-8 LC_CTYPE=UTF-8 The locale module doesn't understand the LC_CTYPE setting, and this appears to be a at best under documented feature of OSX: you can use UTF-8 as the locale name for LC_CTYPE and this is handled sanely by libc. Issue #18378 appears to be related to this. IMHO this is a real bug and should be fixed because the locale module's documentation says it exposes the C library's functionality. -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20999 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20344] subprocess.check_output() docs misrepresent what shell=True does
Tuomas Savolainen added the comment: Made a patch that throws exception as suggested: 3- Make check_output() throw an Exception if the first argument is a list and shell=True -- keywords: +patch nosy: +Tuomas.Savolainen Added file: http://bugs.python.org/file34543/issue20344.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20344 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17128] OS X system openssl deprecated - installer should build local libssl
Ronald Oussoren added the comment: The link below contains a script for building fat binaries for openssl. There's nothing surprising in the script, just building multiple times and then merging the result using lipo. https://gist.github.com/foozmeat/5154962 BTW. I'm not proposing to use that script, at most it could be used for inspiration to enhance the build-installer script. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17128 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21003] how to do batch processing using python
Eric V. Smith added the comment: This bug tracker is for reporting bugs in python. For questions on using python, please use the python-list mailing list: https://mail.python.org/mailman/listinfo/python-list -- nosy: +eric.smith resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21003 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21004] how to store json data into postgresql using python script
New submission from Eric V. Smith: This bug tracker is for reporting bugs in python. For questions on using python, please use the python-list mailing list: https://mail.python.org/mailman/listinfo/python-list -- nosy: +eric.smith resolution: - rejected stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21004 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)
Jovik added the comment: I appreciate your suggestion regarding cygwin, but in the new code base we want to avoid this dependency. Thanks for your time on this issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20927 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21002] _sre.SRE_Scanner object should have a fullmatch() method
Gareth Gouldstone added the comment: Scanner may not be a public interface but it is widely documented, not least on page 67 of the O'reilly Python Cookbook. Even if Scanner is not made public, then surely it should maintain consistency with the public interfaces? -- versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21002 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10240] dict.update.__doc__ is misleading
Changes by Berker Peksag berker.pek...@gmail.com: -- assignee: - docs@python components: +Documentation -Interpreter Core nosy: +berker.peksag, docs@python versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10240 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21005] asyncio.docs : asyncio.subprocess.DEVNULL doc inadequate
New submission from Alexandre JABORSKA: asyncio.subprocess.DEVNULL documentation is the same as asyncio.subprocess.STDOUT one and (I guess) inadequate (cut paste error ?). -- assignee: docs@python components: Documentation messages: 214338 nosy: ajaborsk, docs@python priority: normal severity: normal status: open title: asyncio.docs : asyncio.subprocess.DEVNULL doc inadequate versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21005 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21005] asyncio.docs : asyncio.subprocess.DEVNULL doc inadequate
Roundup Robot added the comment: New changeset 70c77ff64df1 by Victor Stinner in branch 'default': Close #21005: Fix documentation of asyncio.subprocess.DEVNULL http://hg.python.org/cpython/rev/70c77ff64df1 -- nosy: +python-dev resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21005 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21005] asyncio.docs : asyncio.subprocess.DEVNULL doc inadequate
STINNER Victor added the comment: and (I guess) inadequate (cut paste error ?). Correct, my bad. It's now fixed. Thanks for the report. -- nosy: +haypo resolution: fixed - stage: committed/rejected - status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21005 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
New submission from Alexandre JABORSKA: The documentation example (getstatusoutput) does not work on windows because it use the default loop (based on select). The whole asyncio.ProactorEventLoop stuff is not really explained anywhere. Maybe a How to use asyncio on Windows could be useful. -- assignee: docs@python components: Documentation messages: 214341 nosy: ajaborsk, docs@python priority: normal severity: normal status: open title: asyncio.docs : create_subprocess_exec example does not work on windows versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
Roundup Robot added the comment: New changeset 7cca663a72eb by Victor Stinner in branch 'default': Issue #21006: Fix subprocess example on Windows in asyncio doc http://hg.python.org/cpython/rev/7cca663a72eb -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10141] SocketCan support
Vinay Sajip added the comment: What error were you getting? That AF_CAN was undefined (even though HAVE_LINUX_CAN_H is). This is on Ubuntu Jaunty, which I use for my Python core development. Note the change you made in d4ce850b06b7 to fix this problem when it occurred before - it's the same approach as my recent change that we're talking about. It seems that in 3.4, some more instances of AF_CAN usage were added, but wrapped in #ifdef HAVE_LINUX_CAN_H, which led to the new compilation failures. I'll make the changes to take CAN_RAW into account. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10141 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
STINNER Victor added the comment: Oh, the limit parameter StreamReader is not documented! Here is a patch to document it. -- nosy: +gvanrossum, haypo, yselivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
Changes by STINNER Victor victor.stin...@gmail.com: -- keywords: +patch Added file: http://bugs.python.org/file34544/streamreader_limit.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
STINNER Victor added the comment: The whole asyncio.ProactorEventLoop stuff is not really explained anywhere. Maybe a How to use asyncio on Windows could be useful. It is explained in the subprocess methods of the event loop. Well, I expected this reaction: the subprocess documentation is currently splitted in two parts (event loop and asyncio.subprocess). IMO all functions related to subprocess must be moved to the subprocess page. Here is a patch to group all subprocess documentation. I added a Connect pipes section, mentionned that event loop functions are the low level API whereas the asyncio.subprocess is the high level API. -- Added file: http://bugs.python.org/file34545/asyncio_subprocess.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21001] Python 3.4 MSI installer doesn't work
Ram Rachum added the comment: David: It's failing on both of my computers, laptop and desktop, not just one. Don't you guys have a simple command to create an .exe installer? This has a good chance of solving my problem. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21001 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Marc-Andre Lemburg added the comment: On 21.03.2014 00:10, Donald Stufft wrote: We shouldn't do this in Python for the same reason we're not including a predefined set of CA root certificates with the distribution. The difference here is that there are properly maintained alternatives to Python including a predefined set of CA root certificates. This isn't the case with OpenSSL. OpenSSL doesn't provide good defaults and I'm not aware of a single OS which ships with OpenSSL that patches it to provide good defaults. Python exposes this API, it's Python's job to properly secure it. Perhaps I should have clarified this earlier on: I agree to use such defaults for writing SSL servers in Python. I disagree when it comes to SSL clients. If we enforce a specific set of ciphers per default and a user finds that a server he wants to communicate with for example only supports RC4 ciphers, because that's the server admins were told to use after the BEAST attack was found, the user most likely won't be able to fix this. So what's the net result: the scripts doesn't work, without any way to get it back to work again. That's not more secure, it's a failure :-) IMO, Python should make SSL server code use best practices and make it easy to alter the defaults. Python should also make sure that SSL client code works using HIGH level ciphers, but not limit the selection much further or make it more specific (apart from removing completely broken features like e.g. MD5, aNULL, etc.). If we want to enhance the user security, we should educate our users about best practices and provide information on how to implement them, -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: We shouldn't do this in Python for the same reason we're not including a predefined set of CA root certificates with the distribution. The difference here is that there are properly maintained alternatives to Python including a predefined set of CA root certificates. This isn't the case with OpenSSL. OpenSSL doesn't provide good defaults and I'm not aware of a single OS which ships with OpenSSL that patches it to provide good defaults. Python exposes this API, it's Python's job to properly secure it. Perhaps I should have clarified this earlier on: I agree to use such defaults for writing SSL servers in Python. I disagree when it comes to SSL clients. Well Python is already doing that and Python should be doing that. OpenSSL defaults are horrendous. If we enforce a specific set of ciphers per default and a user finds that a server he wants to communicate with for example only supports RC4 ciphers, because that's the server admins were told to use after the BEAST attack was found, the user most likely won't be able to fix this. Luckily my default cipher string still contains RC4 only the restricted best practices one doesn't. Obviously this was only an example but the problem you're arguing against doesn't exist in practice. The cipherstring I've posted is largely similar to the one we already have except it removes a few other ciphers that are either weak or unable to actually be used with the API of the ssl module and it applies an explicit ordering in order to, in the cases the server let's us pick, get the best cipher suite. Let me repeat, this cipher string, compatability wise, is not that different from what is *already* there and contains every moderately secure cipher that is in use. So what's the net result: the scripts doesn't work, without any way to get it back to work again. That's not more secure, it's a failure :-) You can get it back just by passing the ciphers keyword argument to the ssl module. IMO, Python should make SSL server code use best practices and make it easy to alter the defaults. Python should also make sure that SSL client code works using HIGH level ciphers, but not limit the selection much further or make it more specific (apart from removing completely broken features like e.g. MD5, aNULL, etc.). My cipherstring includes all HIGH ciphers and only explicitly excludes MD5, aNULL, eNULL, and DSS. If we want to enhance the user security, we should educate our users about best practices and provide information on how to implement them, Expecting users to properly configure a cipher string in order to get modern best practices when Python itself can do it for practically zero difference in compatibility is user hostile. In many cases those users are not even going to be aware that they are using the ssl module or what OpenSSL even is. To be perfectly honest this set will work with more servers than most browsers will and browsers are typically the kings of bending over backwards not to ever break SSL. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20065] Python-3.3.3/Modules/socketmodule.c:1660:14: error: 'CAN_RAW' undeclared (first use in this function)
Roundup Robot added the comment: New changeset 9dc199b921eb by Vinay Sajip in branch '3.4': Issue #10141, Issue 20065: Changed #if to take CAN_RAW into account. http://hg.python.org/cpython/rev/9dc199b921eb New changeset 20cced06acdd by Vinay Sajip in branch 'default': Issue #10141, Issue 20065: Merged from 3.4. http://hg.python.org/cpython/rev/20cced06acdd -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20065 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10141] SocketCan support
Roundup Robot added the comment: New changeset 9dc199b921eb by Vinay Sajip in branch '3.4': Issue #10141, Issue 20065: Changed #if to take CAN_RAW into account. http://hg.python.org/cpython/rev/9dc199b921eb New changeset 20cced06acdd by Vinay Sajip in branch 'default': Issue #10141, Issue 20065: Merged from 3.4. http://hg.python.org/cpython/rev/20cced06acdd -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10141 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Updated the patch to change the priority slightly to ensure that all the secure PFS ciphers come first and that non PFS AES comes before the other Non PFS HIGH ciphers -- Added file: http://bugs.python.org/file34546/better-ciphers-better-priority.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16047] Tools/freeze no longer works in Python 3
Christian Bachmaier added the comment: Thanks for the patches. After applying issue11824-0.patch and then isse16047-1.patch I am successfully able to freeze a hello world python script under ubuntu 14.04 with python 3.4 rc3. I have attached my new site.py file, since the automatical patch application did not run through. However, in my productive project I need the psycopg2 library for database access. Whenever using 'import psycopg2' in my code the binary shows a runtime error that it cannot find the module psycopg2._psycopg. A one line script suffices for reproduction. Executing the script without freezing it works like a charm. In Python 3.2 it helped to create in the working dir a psycopg2 subdir with a symlink _psycopg.so - /usr/lib/python3/dist-packages/psycopg2/_psycopg.cpython-32mu.so . This seems no longer help. Is this a bug/feature of freeze or psycopg2? Thanks for your interest and help. -- nosy: +chba Added file: http://bugs.python.org/file34547/site.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16047 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Marc-Andre Lemburg added the comment: On 21.03.2014 12:42, Donald Stufft wrote: If we enforce a specific set of ciphers per default and a user finds that a server he wants to communicate with for example only supports RC4 ciphers, because that's the server admins were told to use after the BEAST attack was found, the user most likely won't be able to fix this. Luckily my default cipher string still contains RC4 only the restricted best practices one doesn't. Obviously this was only an example but the problem you're arguing against doesn't exist in practice. The cipherstring I've posted is largely similar to the one we already have except it removes a few other ciphers that are either weak or unable to actually be used with the API of the ssl module and it applies an explicit ordering in order to, in the cases the server let's us pick, get the best cipher suite. Let me repeat, this cipher string, compatability wise, is not that different from what is *already* there and contains every moderately secure cipher that is in use. Ok, here's a test to compare the outcome of your suggestion compared to the defaults used in Python (which are basically the OpenSSL defaults minus the broken parts). I've added !MD5 to the Python cipher string, since that seems to be missing for some reason. Here's the diff (taking order into account): Using OpenSSL 1.0.1f 6 Jan 2014 --- --- standard.txt2014-03-21 13:10:38.451648736 +0100 +++ donald.txt 2014-03-21 13:10:38.491649094 +0100 @@ -1,73 +1,51 @@ ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESGCM(256) Mac=AEAD +ECDH-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH/RSA Au=ECDH Enc=AESGCM(256) Mac=AEAD +ECDH-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AESGCM(256) Mac=AEAD +ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(128) Mac=AEAD +ECDHE-ECDSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESGCM(128) Mac=AEAD +ECDH-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH/RSA Au=ECDH Enc=AESGCM(128) Mac=AEAD +ECDH-ECDSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AESGCM(128) Mac=AEAD +DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD +DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(128) Mac=AEAD ECDHE-RSA-AES256-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AES(256) Mac=SHA384 ECDHE-ECDSA-AES256-SHA384 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AES(256) Mac=SHA384 ECDHE-RSA-AES256-SHASSLv3 Kx=ECDH Au=RSA Enc=AES(256) Mac=SHA1 ECDHE-ECDSA-AES256-SHA SSLv3 Kx=ECDH Au=ECDSA Enc=AES(256) Mac=SHA1 -SRP-DSS-AES-256-CBC-SHA SSLv3 Kx=SRP Au=DSS Enc=AES(256) Mac=SHA1 -SRP-RSA-AES-256-CBC-SHA SSLv3 Kx=SRP Au=RSA Enc=AES(256) Mac=SHA1 -DHE-DSS-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=DSS Enc=AESGCM(256) Mac=AEAD -DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD -DHE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 -DHE-DSS-AES256-SHA256 TLSv1.2 Kx=DH Au=DSS Enc=AES(256) Mac=SHA256 -DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 -DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 -DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(256) Mac=SHA1 -DHE-DSS-CAMELLIA256-SHA SSLv3 Kx=DH Au=DSS Enc=Camellia(256) Mac=SHA1 -ECDH-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH/RSA Au=ECDH Enc=AESGCM(256) Mac=AEAD -ECDH-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AESGCM(256) Mac=AEAD ECDH-RSA-AES256-SHA384 TLSv1.2 Kx=ECDH/RSA Au=ECDH Enc=AES(256) Mac=SHA384 ECDH-ECDSA-AES256-SHA384 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AES(256) Mac=SHA384 ECDH-RSA-AES256-SHA SSLv3 Kx=ECDH/RSA Au=ECDH Enc=AES(256) Mac=SHA1 ECDH-ECDSA-AES256-SHA SSLv3 Kx=ECDH/ECDSA Au=ECDH Enc=AES(256) Mac=SHA1 -AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD -AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 -AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 -CAMELLIA256-SHA SSLv3 Kx=RSA Au=RSA Enc=Camellia(256) Mac=SHA1 -PSK-AES256-CBC-SHA SSLv3 Kx=PSK Au=PSK Enc=AES(256) Mac=SHA1 -ECDHE-RSA-DES-CBC3-SHA SSLv3 Kx=ECDH Au=RSA Enc=3DES(168) Mac=SHA1 -ECDHE-ECDSA-DES-CBC3-SHA SSLv3 Kx=ECDH Au=ECDSA Enc=3DES(168) Mac=SHA1 -SRP-DSS-3DES-EDE-CBC-SHA SSLv3 Kx=SRP Au=DSS Enc=3DES(168) Mac=SHA1 -SRP-RSA-3DES-EDE-CBC-SHA SSLv3 Kx=SRP Au=RSA Enc=3DES(168) Mac=SHA1 -EDH-RSA-DES-CBC3-SHASSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 -EDH-DSS-DES-CBC3-SHASSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 -ECDH-RSA-DES-CBC3-SHA SSLv3 Kx=ECDH/RSA Au=ECDH Enc=3DES(168) Mac=SHA1 -ECDH-ECDSA-DES-CBC3-SHA SSLv3 Kx=ECDH/ECDSA Au=ECDH Enc=3DES(168) Mac=SHA1 -DES-CBC3-SHA
[issue18967] Find a less conflict prone approach to Misc/NEWS
Brett Cannon added the comment: You lose chronology in the directory, but not necessarily in the output; if you sort based on first commit time then you retain the chronological ordering in the merge. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
Alexandre JABORSKA added the comment: I saw the low level part with the warning. But what I mean is that I found no clear indication on how to change default loop to allow asyncio.subprocess usage with Windows Python. I guessed : asyncio.set_event_loop(ProactorEventLoop()) but I'm not sure (it works for me). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: It shows the effect of the additional !DSS - which I don't understand; DSA is part of the X.509 standard, so it's removing support will break compatibility. Could you perhaps explain you're reasoning ? Well DSA has problems with weak RNGs and consequently no CA that I'm aware of will even issue a DSS cert and I've never seen nor heard of anyone actually using them in practice. If it makes you feel better I can add DSS back in. It also shows that by removing DEFAULT, you are not allowing other ciphers. PSK and SRP are not likely to be used by web servers. SEED doesn't appear to have wide spread use either, so leaving it out probably won't matter. Leaving those in doesn't hurt either. I'm pretty sure you can't even use PSK or SRP using the stdlib ssl module, I didn't explicitly exclude them though. It's just a side effect of specifying ECDH, DH, and RSA explicitly. So modulo the DSS question I see your point about compatibility :-) I've uploaded a new patch that removes the !DSS from the default ciphers. Here's the diff from the original default string (with the added !MD5) and my new patch's default string DHE-DSS-SEED-SHASSLv3 Kx=DH Au=DSS Enc=SEED(128) Mac=SHA1 DHE-RSA-SEED-SHASSLv3 Kx=DH Au=RSA Enc=SEED(128) Mac=SHA1 IDEA-CBC-SHASSLv3 Kx=RSA Au=RSA Enc=IDEA(128) Mac=SHA1 PSK-3DES-EDE-CBC-SHASSLv3 Kx=PSK Au=PSK Enc=3DES(168) Mac=SHA1 PSK-AES128-CBC-SHA SSLv3 Kx=PSK Au=PSK Enc=AES(128) Mac=SHA1 PSK-AES256-CBC-SHA SSLv3 Kx=PSK Au=PSK Enc=AES(256) Mac=SHA1 PSK-RC4-SHA SSLv3 Kx=PSK Au=PSK Enc=RC4(128) Mac=SHA1 SEED-SHASSLv3 Kx=RSA Au=RSA Enc=SEED(128) Mac=SHA1 SRP-DSS-3DES-EDE-CBC-SHA SSLv3 Kx=SRP Au=DSS Enc=3DES(168) Mac=SHA1 SRP-DSS-AES-128-CBC-SHA SSLv3 Kx=SRP Au=DSS Enc=AES(128) Mac=SHA1 SRP-DSS-AES-256-CBC-SHA SSLv3 Kx=SRP Au=DSS Enc=AES(256) Mac=SHA1 SRP-RSA-3DES-EDE-CBC-SHA SSLv3 Kx=SRP Au=RSA Enc=3DES(168) Mac=SHA1 SRP-RSA-AES-128-CBC-SHA SSLv3 Kx=SRP Au=RSA Enc=AES(128) Mac=SHA1 SRP-RSA-AES-256-CBC-SHA SSLv3 Kx=SRP Au=RSA Enc=AES(256) Mac=SHA1 Still, OpenSSL might add more ciphers or modes in the future and you'd automatically get those by using DEFAULT in the cipher string, so I'd opt for just adding !MD5 to the default cipher list, i.e. DEFAULT:!aNULL:!eNULL:!MD5:!LOW:!EXPORT:!SSLv2 With such a string, both servers and client get good compatibility, while keeping Python users reasonably safe per default and keeping the maintenance burden out of Python. The (newly uploaded) cipher string is still better because it includes a priority that is import. It prioritizes: PFS Non PFS but Secure Non PFS Secure Slow Security Problematic but for Compatibility This is important especially in the modern age of bulk data collection. It will still pick up new HIGH ciphers added by OpenSSL without any changes made to Python itself. This is better than a blacklist approach because it'd be easy for OpenSSL to add something else bad to DEFAULT that didn't get caught by !aNULL:!eNULL:!MD5:!LOW:!EXPORT:!SSLv2. -- Added file: http://bugs.python.org/file34548/better-ciphers-dss.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: I think the proposed cipher string is still overly complicated and tedious to maintain. The following seems to achieve similar results: 'EECDH+AESGCM:DH+AESGCM:ECDH:DH:HIGH:!aNULL:!eNULL:!MD5:!DSS:!LOW:!EXPORT' Also, as Marc-André points out, we probably shouldn't ban RC4 even from the so-called restricted ciphers. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: I'm pretty sure you can't even use PSK or SRP using the stdlib ssl module, I didn't explicitly exclude them though. This is true. There are issues open, though: issue 11943 and issue 19084. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: (oh, I missed the part where Marc-André suggested not to drop DSS; this should also be removed from my cipher string proposal) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: As I said earlier Antoine, doing that puts PFS RC4 before non PFS AES. That isn't good because RC4 key stream bias makes it extremely fragile. RC4 needs to be in the default ciphers for compatibility sake but it should be dead last so that it's only used as a last ditch effort because it should *not* be considered generally secure anymore. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: With regard to PSK and SRP. Seeing as how Python doesn't currently support them, SRP had a patch that hasn't been worked on since 2011 and PSK doesn't have a patch at all that this cipher string shouldn't concern itself with something that Python might someday in the future gain support for. If someone comes along and adds PSK or SRP support they can adjust the cipher string in that patch, probably by adding the PSK or SRP ciphers conditionally when the parameters that are required for those ciphers are passed into wrap_socket, or maybe just all the time. Point being it shouldn't be a consideration now as adding it later is simple. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: With regard to PSK and SRP. Seeing as how Python doesn't currently support them, SRP had a patch that hasn't been worked on since 2011 and PSK doesn't have a patch at all that this cipher string shouldn't concern itself with something that Python might someday in the future gain support for. I didn't say otherwise. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Yup :) Just being explicit in that! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20344] subprocess.check_output() docs misrepresent what shell=True does
R. David Murray added the comment: Thanks Tuomas, but we don't have any consensus that that kind of change will be accepted. It's just my opinion that it should be...and if it was, it would have to start with a deprecation, not raising an exception. What we need as a patch for this issue is a documentation patch explaining why using shell=True with a list is a bad idea in the 'frequently used arguments' section. The paragraph about 'args' in the frequently used arguments section should say something like 'using shell=True with a list containing more than one element does not currently raise an error, but it will not do what you expect; only the first element of the list will be executed on unix, and on windows the quoting is likely to be incorrect. See the Popen constructor documentation below for a more precise description.' (You can see why I think this usage should be deprecated, I hope ;) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20344 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19995] %c, %o, %x, %X accept non-integer values instead of raising an exception
Roundup Robot added the comment: New changeset e266525c9294 by Ethan Furman in branch 'default': Issue19995: more informative error message; spelling corrections; use operator.mod instead of __mod__ http://hg.python.org/cpython/rev/e266525c9294 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11380] Improve reporting of broken stdout pipe during interpreter shutdown
Changes by Dillon Aumiller dillonaumil...@gmail.com: -- nosy: +daumiller ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11380 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21007] List of development releases in PEPs like 429 should be links to download pages
Changes by Ram Rachum r...@rachum.com: -- assignee: docs@python components: Documentation nosy: cool-RR, docs@python priority: normal severity: normal status: open title: List of development releases in PEPs like 429 should be links to download pages type: behavior versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21007 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21007] List of development releases in PEPs like 429 should be links to download pages
New submission from Benjamin Peterson: I disagree. They are easy enough to find on the website. Easier than the release schedule I hope! Of course, RMs are welcome to link to the download page if they want, but we needn't require it. -- nosy: +benjamin.peterson resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21007 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21000] json.tool ought to have a help flag
Benjamin Peterson added the comment: Very nice, but your help message still doesn't explain what json.tool does. :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21000 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13630] IDLE: Find(ed) text is not highlighted while dialog box is open
Tal Einat added the comment: Im considering updating SearchBar and posting a patch. Marco, any chance you could detail the quirks and bugs you experienced when using SearchBar? -- nosy: +taleinat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13630 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21000] json.tool ought to have a help flag
Antoine Pitrou added the comment: Perhaps this thing should use argparse? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21000 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19714] Add tests for importlib.machinery.WindowsRegistryFinder
Claudiu.Popa added the comment: Hello. Here's a patch for this issue. It tests only the conditions described by Eric. -- keywords: +patch nosy: +Claudiu.Popa Added file: http://bugs.python.org/file34549/issue19714.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19714 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21008] Update devinabox for Python 3.4
New submission from Brett Cannon: E.g. with pip included it makes setting up coverage.py easier. -- assignee: brett.cannon messages: 214371 nosy: brett.cannon priority: low severity: normal stage: needs patch status: open title: Update devinabox for Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21008 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19165] Change formatter warning to DeprecationWarning in 3.5
Roundup Robot added the comment: New changeset 455e5385752a by Brett Cannon in branch 'default': Issue #19165: The formatter module graduates to full deprecation. http://hg.python.org/cpython/rev/455e5385752a -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19165 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18967] Find a less conflict prone approach to Misc/NEWS
Zachary Ware added the comment: R. David Murray wrote: I want no script asking me questions. Post-facto errors for omissions are fine (and if I have to positively say no in the input file, that's fine). tkinter is right out. I have been planning a command line interface, something along the lines of `news.py --issue 12345 --section Core --message Converted ham to spam`. Of course, there would be short options as well. The interactive interface was just what I wrote first because it seemed easiest at the time :). Adding the command line part shouldn't be too hard with argparse, though; I'll see if I can do it this afternoon. If you *also* want to make a script that asks questions (or even a tkinter ap), that's fine, but it should not be the main interface, it should be a wrapper. I'm fine with that. One thing I really don't like about the separate file approach is that you lose the obvious chronology. It's probably not a blocker, but it is definitely a disadvantage. If we give the .news files names of the form nnn-issuex.news where 'nnn' is the number of .news files that already exist in the target folder (or the whole tree) and -issuex is only present if an issue number was given, chronology would be kept, though it might get a bit hairy merging between branches. It would be unlikely to have actual merge conflicts (unless your news entry wasn't linked to an issue), but might cause things to get a bit out of order. Assuming a satisfactory interface to give news.py the proper information and a good resolution to the chronology issue, how do you feel about the rest of the approach? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19165] Change formatter warning to DeprecationWarning in 3.5
Changes by Brett Cannon br...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19165 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20884] importlib/__init__.py can not be loaded without __file__ - breaks cxFreeze
Roundup Robot added the comment: New changeset b5b81a3eb6e6 by Brett Cannon in branch '3.4': Issue #20884: Don't assume in importlib.__init__ that __file__ is http://hg.python.org/cpython/rev/b5b81a3eb6e6 New changeset 42ae7b2524a2 by Brett Cannon in branch 'default': Merge for issue #20884 http://hg.python.org/cpython/rev/42ae7b2524a2 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20884 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20884] importlib/__init__.py can not be loaded without __file__ - breaks cxFreeze
Changes by Brett Cannon br...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20884 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20884] importlib/__init__.py can not be loaded without __file__ - breaks cxFreeze
Jurko Gospodnetić added the comment: Thanks Brett! :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20884 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20627] Add context manager support to xmlrpc.client.ServerProxy
Roundup Robot added the comment: New changeset 395904f70d6a by Brett Cannon in branch 'default': Issue #20627: xmlrpc.client.ServerProxy is now a context manager. http://hg.python.org/cpython/rev/395904f70d6a -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20627 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20627] Add context manager support to xmlrpc.client.ServerProxy
Brett Cannon added the comment: Thanks for the patch! -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20627 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20627] Add context manager support to xmlrpc.client.ServerProxy
Claudiu.Popa added the comment: My pleasure! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20627 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18566] In unittest.TestCase docs for setUp() and tearDown() don't mention AssertionError
Nitika Agarwal added the comment: Hi, I am attaching a patch with the changes made as suggested by py.user. -- nosy: +nitika Added file: http://bugs.python.org/file34550/document18566.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18566 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21009] Potential deadlock in concurrent futures when garbage collection occurs during Queue.get
New submission from Simon Jagoe: At Enthought we have been tracking a deadlock in some code that turned out to be due to the following scenario: 0) There is some cyclic garbage that requires collection; an object in the garbage is referred to by a weakref with a callback 1) You have a lock that is acquired 2) While the lock is held, the garbage collector runs (on the same thread) 3) The weakref callback in (0) is called via the garbage collecter and the callback tries to acquire the same lock that was acquired in (1) Attached is a simple script that exercises the issue in Python 3.3. The script monkey-patches Queue.get to force garbage collection after acquiring the Queue.not_empty lock. -- components: Library (Lib) files: executor-hang.py messages: 214380 nosy: simon.jagoe priority: normal severity: normal status: open title: Potential deadlock in concurrent futures when garbage collection occurs during Queue.get type: behavior versions: Python 3.3, Python 3.4 Added file: http://bugs.python.org/file34551/executor-hang.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21009 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21009] Potential deadlock in concurrent futures when garbage collection occurs during Queue.get
Changes by Mark Dickinson dicki...@gmail.com: -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21009 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21010] asyncio doc typo
New submission from Claudiu.Popa: There is an invalid item meth:`resume_reading`. -- assignee: docs@python components: Documentation files: asyncio_doc_fix.patch keywords: patch messages: 214381 nosy: Claudiu.Popa, docs@python priority: normal severity: normal status: open title: asyncio doc typo versions: Python 3.5 Added file: http://bugs.python.org/file34552/asyncio_doc_fix.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21010 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21009] Potential deadlock in concurrent futures when garbage collection occurs during Queue.get
Changes by Chris Farrow farro...@gmail.com: -- nosy: +Chris.Farrow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21009 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21008] Update devinabox for Python 3.4
Changes by Brett Cannon br...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21008 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21005] asyncio.docs : asyncio.subprocess.DEVNULL doc inadequate
Roundup Robot added the comment: New changeset 230510d0cb92 by Victor Stinner in branch '3.4': Close #21005: Fix documentation of asyncio.subprocess.DEVNULL http://hg.python.org/cpython/rev/230510d0cb92 -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21005 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21006] asyncio.docs : create_subprocess_exec example does not work on windows
Roundup Robot added the comment: New changeset ab0aa412fca2 by Victor Stinner in branch '3.4': Issue #21006: Fix subprocess example on Windows in asyncio doc http://hg.python.org/cpython/rev/ab0aa412fca2 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21006 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21010] asyncio doc typo
Roundup Robot added the comment: New changeset ef4f460e3c9e by Victor Stinner in branch '3.4': Close #21010: Fix typo in asyncio doc. Patch written by Claudiu Popa. http://hg.python.org/cpython/rev/ef4f460e3c9e New changeset 7761b3dff2e8 by Victor Stinner in branch 'default': (Merge 3.4) Close #21010: Fix typo in asyncio doc. Patch written by Claudiu http://hg.python.org/cpython/rev/7761b3dff2e8 -- nosy: +python-dev resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21010 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21010] asyncio doc typo
STINNER Victor added the comment: Fix applied, thanks. -- nosy: +haypo stage: committed/rejected - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21010 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21007] List of development releases in PEPs like 429 should be links to download pages
Ram Rachum added the comment: I looked for it for 10 minutes but couldn't find the link. I ended up using a URL from an old script. I still don't know how I was supposed to find it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21007 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: Ok, so I think the latest patch is mostly good but I don't understand why the restricted ciphers (again, misnomer) would ban RC4 (and DSS?). These are the ciphers used by higher-level client libs, and connection failures will confuse the hell out of people. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19714] Add tests for importlib.machinery.WindowsRegistryFinder
Changes by Claudiu.Popa pcmantic...@gmail.com: Added file: http://bugs.python.org/file34553/issue19714.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19714 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21011] PyArg_ParseTupleAndKeywords doesn't take const char *keywords[]
New submission from Hristo Venev: This really annoys me. I have to store the literals in char[] and then make a char*[] from them. It would be better if a simple array of string literals could be used. It would also require less data space because string literals could be merged by the compiler. I don't know why PyArg_ParseTupleAndKeywords would ever modify the keywords array so it makes absolutely no sense to me for the array not to be const char*[]. In all cases I have seen PyArg_ParseTupleAndKeywords being used string literals were converted to char* (dropping const) which is far far worse than inefficient code. -- components: Extension Modules messages: 214388 nosy: h.venev priority: normal severity: normal status: open title: PyArg_ParseTupleAndKeywords doesn't take const char *keywords[] type: resource usage versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21011 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21001] Python 3.4 MSI installer doesn't work
Zachary Ware added the comment: I've used the same installer on multiple machines with no problems, as have many others; this leads me to believe that there is no problem with the MSI :) Did you use the same MSI file on both machines? Try re-downloading, or checking the size and md5sum of the file (both are listed on the download page). And no, there is no simple way to make an .exe installer. I'm unconvinced that it would fix your problem anyway; why would that make a difference? Your problem here is better discussed on python-list or python-win32; I'm closing this issue. If you can point out a legitimate bug with steps to reproduce the problem, please reopen. -- nosy: +zach.ware resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21001 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21012] Figure out how to best leverage pip in devinabox
New submission from Brett Cannon: Probably the most complicated bit now for using devinabox is building the various bits of docs in a way that doesn't require mucking with the system python: * Having Python built * Creating a venv * Installing sphinx * Running the requisite Makefile with the proper envvar overridden to point to the venv I see a couple of ways of handling this: * Assume people know how to do the above * Verbally instruct people on how to do these steps * Provide a requirements.txt file for sphinx and coverage -- two birds w/ one stone =) -- and instruct on how to install from that * Provide a setup_venv script and then instruct on the doc building * Provide a build.py script which takes named commands like 'docs', 'peps', etc. and then does the right thing automatically There is also the question of whether any of this should make its way up into the devguide, etc. My gut says that we should rename README to SPRINT_LEADERS and then provide a README for the sprint participants which lays out the commands along with comments on where to learn more about what's going on. We don't have to advertise that the doc is actually a shell script that we can use to verify the steps are all correct. =) This way they have to grasp the concept of how to build, make a venv, use pip, etc. We can also make sure that there are no documentation holes outside of devinabox for any one step. Another way to utilize pip is to use it to download all the files necessary to build the docs and get coverage so that offline installations can occur. Not sure what's the easiest way to make pip just download projects and their deps in a way that allows for easily pointing pip at something and say install from here, but I suspect there's a way (using just wheels is a little tricky as markupsafe has an accelerator and coverage has to be compiled). IOW how do we get contributors using venv and pip effectively w/o training them only on how to do things in a devinabox instance? -- messages: 214390 nosy: brett.cannon, ncoghlan, r.david.murray priority: low severity: normal stage: needs patch status: open title: Figure out how to best leverage pip in devinabox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21012 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10141] SocketCan support
Charles-François Natali added the comment: That AF_CAN was undefined (even though HAVE_LINUX_CAN_H is). This is on Ubuntu Jaunty, which I use for my Python core development. How dear... The latest change should be OK. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10141 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21012] Figure out how to best leverage pip in devinabox
Donald Stufft added the comment: Right now you can do ``pip install --download some/path --no-use-wheel stuff`` and then ``pip install --no-index --find-links some/path stuff`` In the future that'll be ``pip download`` instead probably. -- nosy: +dstufft ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21012 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Note: The RC4 and DSS exclusion existed previously on the restricted ciphers so we'd have to ask Christian why he did that. For me personally the restricted ciphers are intended to be best practice ciphers and that means no RC4. DSS here I'm kind of meh about the same way I was for the default ciphers. DSA has historically had problems with weak RNGs and as far as I'm aware no CA's actually issue DSS certificates. But I mostly left !DSS in the restricted set because Christian had it in originally. This might be a case where to really do best practices we need to diverge between client and server. For a server I definitely think putting RC4 in the cipher string is a bad thing. For clients it is not the greatest thing but it more closely matches what browsers do because there are a few services here and there which only expose RC4. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Forgot to add! If you think splitting between restricted server and client ciphers I can split them like that and upload a new patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21000] json.tool ought to have a help flag
Berker Peksag added the comment: Here's a new patch. Changes: - Updated the output of -h option - Added documentation - Switched to argparse -- Added file: http://bugs.python.org/file34554/issue21000_v2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21000 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: Forgot to add! If you think splitting between restricted server and client ciphers I can split them like that and upload a new patch. I was about to open a separate issue for the server side. How about restricting this issue to client usage? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18378] locale.getdefaultlocale() fails on Mac OS X with default language set to English
Ned Deily added the comment: Ronald or Dmitry, can you elaborate under what conditions you start your login shell on 10.9? I cannot reproduce the behavior you observe. With 10.9 Terminal.app and the default language settings in System Preferences and with the default Terminal.app preferences, specifically Settings - (Profile) - Advanced - Character encoding - Unicode (UTF-8) and Set LANG environment variable on startup checked, login sessions have LANG=en_US.UTF-8 defined and LC_CTYPE is not defined at all. Are you sure that isn't begin created by a shell profile somewhere? (I can't check earlier OS X releases at the moment.) That said, I agree that, if OS X accepts UTF-8 as a valid locale, the locale module should, too. -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18378 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20999] setlocale, getlocale succession -- ValueError or (None, None)
Ned Deily added the comment: OK, let's close this issue as a duplicate of Issue18378 and continue the discussion there. -- resolution: works for me - duplicate status: open - closed superseder: - locale.getdefaultlocale() fails on Mac OS X with default language set to English ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20999 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20942] _frozen_importlib should not have a __file__ attribute
Brett Cannon added the comment: Here is a patch to change PyImport_ImportFrozenModuleObject() to not set __file__. Had to refactor some things as PyImport_ExecCodeModuleObject() was setting __file__ no matter what, so to avoid it even being used during import I had to change some things. -- keywords: +patch stage: test needed - patch review Added file: http://bugs.python.org/file34555/no_frozen__file__.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20942 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16047] Tools/freeze no longer works in Python 3
Brett Cannon added the comment: Did you want to update your patch for Python 3.4 and 3.5, Meador? -- versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16047 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Not sure what you mean by client issue. Do you mean to keep RC4? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: Which client issue? Sorry, I've lost track :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Donald Stufft added the comment: Er, I typed issue and meant usage. Right now the only difference between restricted ciphers and the default ciphers is restricted ciphers have no RC4 and no DSS. You wanted this issue limited to client changes and I'm not sure how to do that without enabling RC4/DSS for servers (which is a regression in the security of the restricted ciphers). I think if we want to make restricted ciphers apply only for servers that's OK but as this ticket doesn't change the restrictions (other than omitting SRP/PSK and SEED/IDEA) that there's no changes to be made here, it should be accepted and then another ticket for restricting the restricted ciphers to servers only? Or what did you have in mind? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20995] Use Better Default Ciphers for the SSL Module
Antoine Pitrou added the comment: Er, I typed issue and meant usage. Right now the only difference between restricted ciphers and the default ciphers is restricted ciphers have no RC4 and no DSS. You wanted this issue limited to client changes and I'm not sure how to do that without enabling RC4/DSS for servers (which is a regression in the security of the restricted ciphers). Hmm, fair enough, let's change them all at once here. Also, since restricted ciphers aren't actually used by stdlib modules, I changed my mind and think it's ok to disable RC4 and DSS :-) I'll still open another issue for server-specific configuration: not the ciphers, but other stuff. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20913] Standard Library documentation needs SSL security best practices doc.
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +dstufft ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20913 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21007] List of development releases in PEPs like 429 should be links to download pages
Ned Deily added the comment:
AFAIK, traditionally, there have not been separate download pages for each
pre-release of a new feature (e.g. 3.4.0) or maintenance (e.g. 3.3.5) release.
The usual practice has been to create *one* release page at the usual URI (e.g.
https://www.python.org/download/releases/3.3.5) for the first pre-release
(alpha, beta, or rc) and then update the contents of that page for each
subsequent pre-release through the final release. The download links for the
bits of earlier pre-releases are replaced on the page by those of later
pre-releases or the final release. Thus, even though the pre-release bits are
still available to download at their original URIs, the links to them are no
longer provided on a download page. With the transition to the new python.org
website near the end of the 3.4.0 release cycle, there were some experiments
and changes in process. In particular, separate download pages *were* created
for 3.4.0rc{1,2,3} but not for earlier pre-releases of 3.4.0. There is no g
uarantee at the moment that that will happen again for future releases. If it
is important that there be download links for pre-release bits, the release
process needs to change and someone would need to go back and re-create those
for previous releases somewhere.
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21007
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21013] server-specific SSL context configuration
New submission from Antoine Pitrou: Currently, create_default_context() doesn't do anything special for server use. It seems the configuration could be improved, though: - PROTOCOL_TLSv1 is suboptimal for servers: a TLSv1 server can't accept a TLSv1.2 client, but a SSLv23 server will; so we should use PROTOCOL_SSLv23 (!) - we could enable ECDH by calling SSLContext.set_ecdh_curve(something) -- components: Library (Lib) messages: 214405 nosy: christian.heimes, dstufft, pitrou priority: normal severity: normal status: open title: server-specific SSL context configuration type: enhancement versions: Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21013 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20421] expose SSL socket protocol version
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +dstufft ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20421 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21013] server-specific SSL context configuration
Antoine Pitrou added the comment: (also perhaps enable OP_CIPHER_SERVER_PREFERENCE, although it seems it could cause interoperability problems with some clients) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21013 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21013] server-specific SSL context configuration
Donald Stufft added the comment: Nah it should be fine to enable that, and it's preferable to do so. The server selects the cipher anyways in the TLS handshake. That just tells the server to prefer it's list for precedence and not the client list. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21013 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17846] Building Python on Windows - Supplementary info
Zachary Ware added the comment: No, 3.4 uses VS 2010. Your patch changes the line from hg update 3.4 to hg update 3.3, which is not a legitimate change, in fact it undoes a change that Éric Araujo just made. With the release of 3.4.0, 3.4 became the current maintenance branch and 3.3 moved into security fix only mode, so we want the devguide discussion of maintenance branches to deal with 3.4. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17846 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17621] Create a lazy import loader mixin
Brett Cannon added the comment: New patch that includes docs and integrates the tests. If someone who understands import can look it over and give me an LGTM that would be appreciated. -- Added file: http://bugs.python.org/file34556/lazy_loader.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17621 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20884] importlib/__init__.py can not be loaded without __file__ - breaks cxFreeze
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20884 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19995] %c, %o, %x, %X accept non-integer values instead of raising an exception
Ethan Furman added the comment: Final status: 3.4 - DeprecationWarning 3.5 - TypeError -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19995 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13630] IDLE: Find(ed) text is not highlighted while dialog box is open
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13630 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20956] tokenize module claims tokenize.tokenize returns namedtuple, but it doesn't
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20956 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
