[issue21793] httplib client/server status refactor
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- assignee: rhettinger - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21793 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22477] GCD in Fractions
gladman added the comment: I notice on the documentation for Python 3.5 that this proposed addition is not mentioned. Is it still the intention to add this proposed change to Python 3.5? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22477 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9536] defaultdict doc makes incorrect reference to __missing__ method
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9536 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15178] Doctest should handle situations when test files are not readable
Bohuslav Slavek Kabrda added the comment: Attaching a new version of patch: - Rebased to latest default branch - Simplified prints - Using OSError instead of IOError Hopefully this is the final version :) -- Added file: http://bugs.python.org/file37421/doctest-dont-end-with-exception-on-unreadable-files-v6.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15178 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21793] httplib client/server status refactor
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21793 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22477] GCD in Fractions
STINNER Victor added the comment: I see that the issue #22486 is still open. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22477 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22486] Add math.gcd()
STINNER Victor added the comment: What's the status of this issue? See also the issue #22477. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22486 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Ned Deily added the comment: The changes for 3.4 are incomplete: import ssl Traceback (most recent call last): File stdin, line 1, in module File /py/dev/34/source/Lib/ssl.py, line 122, in module from _ssl import PROTOCOL_SSLv3, PROTOCOL_SSLv23, PROTOCOL_TLSv1 ImportError: cannot import name 'PROTOCOL_SSLv3' For the default (3.5) branch, f776771ab0ee for Issue21068 changed ssl.py to handle missing SSLv3 support; 3.4 needs something similar. -- resolution: fixed - stage: resolved - needs patch status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22486] Add math.gcd()
Serhiy Storchaka added the comment: Here is a patch which addresses both Mark's suggestions. * math.gcd() now work with arbitrary Python objects implementing __index__. * fractions.gcd() and Fraction's constructor now use math.gcd() if both arguments are int, but also support non-ints (e.g. Fractions or floats). * fractions.gcd() now is deprecated. But before committing I want to experiment with simpler implementation and compare it with current complex implementation. If the difference will be not too large, we could use simpler implementation. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22486 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22486] Add math.gcd()
Changes by Serhiy Storchaka storch...@gmail.com: Added file: http://bugs.python.org/file37422/lehmer_gcd_8.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22486 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17914] add os.cpu_count()
Mark Summerfield added the comment: In message http://bugs.python.org/issue17914#msg188626 Victor Stenner says On Windows, GetSystemInfo() is called instead of reading an environment variable. I suppose that this function is more reliable. From my reading, and based on feedback from one of my customers, I believe he is correct and that GetSystemInfo() ought to be used on Windows. (It is available in pywin32 win32api.) -- nosy: +mark ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17914 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Roundup Robot added the comment: New changeset 773e55c95703 by Victor Stinner in branch '3.4': Issue #22935: Fix ssl module when SSLv3 protocol is not supported https://hg.python.org/cpython/rev/773e55c95703 New changeset fb1ffd40d33e by Victor Stinner in branch 'default': Issue #22935: Fix test_ssl when the SSLv3 protocol is not supported https://hg.python.org/cpython/rev/fb1ffd40d33e -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Roundup Robot added the comment: New changeset f0297263a1e8 by Victor Stinner in branch '3.4': Issue #22935: Fix test_ssl when the SSLv3 protocol is not supported https://hg.python.org/cpython/rev/f0297263a1e8 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: The changes for 3.4 are incomplete Ok, I fixed most obvious issues. There is a major severe issue in Lib/ssl.py: def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None): ... This line fails if PROTOCOL_SSLv3 name does not exist. I propose to use PROTOCOL_SSLv23 by default if PROTOCOL_SSLv3 does not exist, as done in Python 3.5. See attached patch. A better option (more secure?) is to use PROTOCOL_SSLv23 by default. What do you think? I prefer to switch to PROTOCOL_SSLv23 by default in Python 3.4. -- Added file: http://bugs.python.org/file37423/get_server_certificate_sslv3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: Oh, in Python 3.4, create_default_context() uses PROTOCOL_SSLv23, SSLSocket, wrap_socket() and _create_unverified_context() use PROTOCOL_SSLv23 by default. In Python 3.5, get_server_certificate() now uses PROTOCOL_SSLv23 by default because test_ssl failed on the host svn.python.org: see issue #20896. changeset: 90360:55f62fa5bebc user:Antoine Pitrou solip...@pitrou.net date:Wed Apr 16 18:56:28 2014 +0200 files: Doc/library/ssl.rst Lib/ssl.py Lib/test/test_ssl.py Misc/NEWS description: Issue #20896: ssl.get_server_certificate() now uses PROTOCOL_SSLv23, not PROTOCOL_SSLv3, for maximum compatibility. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17914] add os.cpu_count()
STINNER Victor added the comment: From my reading, and based on feedback from one of my customers, I believe he is correct and that GetSystemInfo() ought to be used on Windows. (It is available in pywin32 win32api.) Please open a new issue to suggest this enhancement, this issue is closed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17914 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: get_server_certificate_sslv23.patch: Patch to use PROTOCOL_SSLv23 by default in get_server_certificate(), as done in Python 2.7 and 3.5. -- Added file: http://bugs.python.org/file37424/get_server_certificate_sslv23.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23036] Crash Error?
New submission from E Roberts: New to the world of Python. The picture attached is an error that a teacher at my school is receiving when he tries to run anything in IDLE. I know nothing about coding/python/idle or anything of that nature. Sorry I am of little help. Please can someone help me out with this error and provide any help or an answer. Thank you for dealing with a complete novice. -- components: IDLE files: python error.png messages: 232531 nosy: E.Roberts priority: normal severity: normal status: open title: Crash Error? type: crash versions: Python 3.3 Added file: http://bugs.python.org/file37425/python error.png ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23036 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23036] Crash Error?
STINNER Victor added the comment: The problem is that your student created a file called random.py which conflicts with the module random of the Python standard library. Please rename the random.py file to random.py and remove .pyc files (ex: random.pyc or __pycache__/random*pyc). -- nosy: +haypo resolution: - not a bug status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23036 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15267] tempfile.TemporaryFile and httplib incompatibility
STINNER Victor added the comment: Catching TypeError on len() looks as an ugly test to check if body is a string. Why not doing the opposite: first to call fileno() and call AttributeError? Or even use hasattr(body, fileno)? -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15267 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15267] tempfile.TemporaryFile and httplib incompatibility
STINNER Victor added the comment: issue15267.patch: I would feel more confortable if test_send_tempfile() ensures that the socket contains the file content. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15267 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18028] Warnings with -fstrict-aliasing
Roundup Robot added the comment: New changeset 9565b56a4615 by Victor Stinner in branch '2.7': Issue #18028: Fix aliasing issue in READ_TIMESTAMP() of ceval.c on x86_64, https://hg.python.org/cpython/rev/9565b56a4615 New changeset adb445578995 by Victor Stinner in branch '3.4': Issue #18028: Fix aliasing issue in READ_TIMESTAMP() of ceval.c on x86_64, https://hg.python.org/cpython/rev/adb445578995 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18028 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18028] Warnings with -fstrict-aliasing
STINNER Victor added the comment: 3 core developers reviewed Christian's patch, so it also looks good to me :-) Since Christian looks to be busy, I commited his patch. Thanks Christian for your fix. We might enable -fstrict-aliasing later, at least to compile Python core (not to build extensions). -- nosy: +haypo resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18028 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Changes by STINNER Victor victor.stin...@gmail.com: -- title: -c: Line causing exception not shown for exceptions other than SyntaxErrors - python -c: Line causing exception not shown for exceptions other than SyntaxErrors ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
STINNER Victor added the comment: SyntaxError exceptions have a text attribute which contains the line where the error occurred. It's really a special case. For other exceptions, Python only knows that the error occurred in the file called string. Being able to display the line for any exception requires a complex development. I'm not interested to implement it, I don't think that it's very useful (compared to the time needed to develop it). -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23034] Dynamically control debugging output
Antoine Pitrou added the comment: Also this debug output should be printed on stderr, not stdout. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23034 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23034] Dynamically control debugging output
STINNER Victor added the comment: Debugging output switched by Py_REF_DEBUG is now enabled only when -X showrefcount is specified (issue17323). Yes, I like the idea of doing that for other debug options. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23034 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23037] cpu_count() unreliable on Windows
New submission from Mark Summerfield: In message http://bugs.python.org/issue17914#msg188626 Victor Stenner says On Windows, GetSystemInfo() is called instead of reading an environment variable. I suppose that this function is more reliable. From my reading, and based on feedback from one of my customers, I believe he is correct and that GetSystemInfo() ought to be used on Windows. (It is available in pywin32 win32api.) -- components: Library (Lib), Windows messages: 232540 nosy: mark, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open type: behavior versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17914] add os.cpu_count()
Mark Summerfield added the comment: Since this is closed I've created a new issue as requested: http://bugs.python.org/issue23037 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17914 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Marc-Andre Lemburg added the comment: Please always use PROTOCOL_SSLv23 since this is the only forward compatible way of telling OpenSSL to use the best protocol available. Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version to that one protocol version, whereas PROTOCOL_SSLv23 means to use any protocol starting with SSLv2. In the context options you can then disable SSLv2 and SSLv3 to e.g. have the connection use TLS 1.0 or later. -- nosy: +lemburg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Kurt Roeckx added the comment: So this seems to be a function that just gets the certificate? You need to be careful with this since a server could perfectly decide to send a different certificate depending on the client hello it receives. Like if you support ECDSA it might decide to send you the ECDSA certificate instead of the RSA certificate. Or maybe you're even connecting to a different IP address? In any case, you should always use SSLv23, stop supporting anything else. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23037] cpu_count() unreliable on Windows
STINNER Victor added the comment: The code getting the number of processors on Windows is different between the multiprocessing (Python 3.3) and os (Python 3.5) modules. multiprocessing (old code): try: num = int(os.environ['NUMBER_OF_PROCESSORS']) except (ValueError, KeyError): num = 0 os (new code): SYSTEM_INFO sysinfo; GetSystemInfo(sysinfo); ncpu = sysinfo.dwNumberOfProcessors; os.cpu_count() is already implemented with GetSystemInfo() in Python 3.5, so this issue can be closed. Thanks for the reminder Mark, it was useful to double check. If you want to take a look at the source code: https://hg.python.org/cpython/file/35b7dde7fd53/Modules/posixmodule.c#l16064 -- nosy: +haypo resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: So this seems to be a function that just gets the certificate? You need to be careful with this since a server could perfectly decide to send a different certificate depending on the client hello it receives. (...) In any case, you should always use SSLv23, stop supporting anything else. I don't understand. You say that depending on the protocol, you may get a different certificate, and then that we should stop supporting multiple protocol. Does it mean that you ask to remove a Python feature? Even if it is technically possible to return a different certificate, I don't think that much servers will return a different certificate if the client uses SSLv23 instead of SSLv3. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version to that one protocol version, whereas PROTOCOL_SSLv23 means to use any protocol starting with SSLv2. In the context options you can then disable SSLv2 and SSLv3 to e.g. have the connection use TLS 1.0 or later. get_server_certificate() uses _create_unverified_context() (In Python 2.7, 3.4 3.5) which explicitly disable SSLv2 and SSLv3. I still have trouble to understand which protocol will be negociated. We use SSLv3 and disable SSLv3, so the server can only use SSLv23. Am I right? https://docs.python.org/dev/library/ssl.html#ssl.wrap_socket -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Kurt Roeckx added the comment: SSLv3 does not support the TLS extensions so it's going to send a totally different Client Hello. It will for instance not indicate with elliptic curves it supports. So yes the behavior for SSLv3 and SSLv23 can be totally different. But even with both SSLv23 and a different cipher list you can get a different certificate. So what I'm really saying is that if you have an API to get a certificate that creates a new connection and you can set the options for that connection too that you need to document that properly that you might get a different certificate. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
STINNER Victor added the comment: Do you have an example of server returning a different certificate depending on the protocol? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23014] Don't have importlib.abc.Loader.create_module() be optional
Brett Cannon added the comment: I don't think we really need to say anything. If people want default results, simply return None (which is handled for them by importlib.abc.Loader). The only thing changing here is that the method will now be required instead of optional. I'll post the patch here before I commit to make sure it's all clear. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23014 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23038] #python.web irc channel is dead
New submission from Collin Anderson: Can we remove references to #python.web? I assume it was a flourishing channel at some point. https://docs.python.org/3/howto/webservers.html#other-notable-frameworks -- assignee: docs@python components: Documentation messages: 232550 nosy: collinanderson, docs@python priority: normal severity: normal status: open title: #python.web irc channel is dead versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23038 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Marc-Andre Lemburg added the comment: STINNER Victor added the comment: Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version to that one protocol version, whereas PROTOCOL_SSLv23 means to use any protocol starting with SSLv2. In the context options you can then disable SSLv2 and SSLv3 to e.g. have the connection use TLS 1.0 or later. get_server_certificate() uses _create_unverified_context() (In Python 2.7, 3.4 3.5) which explicitly disable SSLv2 and SSLv3. I still have trouble to understand which protocol will be negociated. We use SSLv3 and disable SSLv3, so the server can only use SSLv23. Am I right? https://docs.python.org/dev/library/ssl.html#ssl.wrap_socket I'm not sure what OpenSSL will do if you tell it to use protocol SSLv3 and then disable this via the options again. This sounds like it won't connect at all, since PROTOCOL_SSLv3 means: only support SSLv3 :-) The logic used for protocol selection in OpenSSL is, well, weird. You have the choice between fixing one single protocol version or selecting a range and then disabling certain protocol versions when configuring the context options. FWIW: The ssl_version parameter in _create_unverified_context() already uses the correct default; IMO, exposing the parameter in get_server_certificate() is fairly useless, unless you want to (ab)use the function to test supported protocol versions :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22935] Disabling SSLv3 support
Kurt Roeckx added the comment: Most such sites actually seem to have dropped support for SSLv3. One site where it depends on the cipher string is bugs.cdburnerxp.se -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22935 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23034] Dynamically control debugging output
Serhiy Storchaka added the comment: Here is (conceivably incomplete) list of debugging and tracing output (but not error reporting) from C code. Controlled output. Import and shutdown details -- controlled by the -v flag. Parser tracing -- controlled by the -d flag. If Py_REF_DEBUG is defined -- controlled by the -X showrefcount flag. If PYMALLOC_DEBUG is defined -- controlled by the PYTHONMALLOCSTATS environment variable. If Py_TRACE_REFS is defined -- controlled by the PYTHONDUMPREFS environment variable. Garbage collecting details -- controlled by gc.set_debug(). If LLTRACE is defined -- controlled by the __ltrace__ global variable. Uncomtrolled output. To stderr: In PyType_ClearCache (Objects/typeobject.c) if MCACHE_STATS is defined. Lists allocations if SHOW_ALLOC_COUNT is defined. Tuples allocations if SHOW_TRACK_COUNT is defined. Interned strings statistics if __INSURE__ is defined. In Python/ceval.c if WITH_TSC is defined. In _PyHash_Fini if Py_HASH_STATS is defined. To stdout: In Modules/_ctypes/malloc_closure.c if MALLOC_CLOSURE_DEBUG is defined. Regex matching trace in Modules/_sre.c if VERBOSE is defined. Statistics in Modules/hashtable.c if Py_DEBUG is defined. Allocation counts if COUNT_ALLOCS is defined. There is also dead code in Parser/parsetok.c, Parser/tokenizer.c, Python/pyarena.c, Python/compile.c, Python/formatter_unicode.c, Modules/_elementtree.c, Modules/_tkinter.c, Objects/unicodeobject.c. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23034 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23038] #python.web irc channel is dead
Roundup Robot added the comment: New changeset 1edff7001f58 by Benjamin Peterson in branch '2.7': remove reference to dead irc channel (closes #23038) https://hg.python.org/cpython/rev/1edff7001f58 New changeset aba5f771f5ec by Benjamin Peterson in branch '3.4': remove reference to dead irc channel (closes #23038) https://hg.python.org/cpython/rev/aba5f771f5ec -- nosy: +python-dev resolution: - fixed stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23038 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23039] File name restriction on Windows
New submission from Philip Lee: when using open(filename, 'w') on Windows , File names are not allowed to contain any characters in \/:*?| , however open(filename, 'w') doesn't throw any exceptions when the file name contains these characters . I think some warning should be written in the documentation or exceptions thrown should happen when the file name contains these characters . -- components: IO messages: 232555 nosy: iMath priority: normal severity: normal status: open title: File name restriction on Windows type: enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23039 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23040] Better documentation for the urlencode safe parameter
New submission from Wojtek Ruszczewski: The documentation for urlencode() [1] isn't very clear on how the safe parameter is used, it would better not list it together with encoding and error as only applying to strings. [1] https://docs.python.org/3.5/library/urllib.parse.html#urllib.parse.urlencode -- assignee: docs@python components: Documentation files: urlencode-safe.diff keywords: patch messages: 232556 nosy: docs@python, wrwrwr priority: normal severity: normal status: open title: Better documentation for the urlencode safe parameter type: enhancement versions: Python 3.5 Added file: http://bugs.python.org/file37426/urlencode-safe.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23040 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23039] File name restriction on Windows
R. David Murray added the comment: The argument to open is a path. Some of those characters have a meaning in a path. I ran a couple of quick experiments: ab*c.txt fails with an exception. :16.txt created a file, which I can do an 'ls' and cat (but not rm) on in git-bash, but I'm not sure where it actually is in the file system. Open is just calling the OS to do the open, so if no error is raised, the *OS* (Windows) is not raising the error. I don't think there is a bug here, unless it is in Windows itself. -- components: +Windows nosy: +r.david.murray, steve.dower, tim.golden, zach.ware ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23039 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23040] Better documentation for the urlencode safe parameter
R. David Murray added the comment: The current documentation looks very clear to me, and I don't understand your changed version. Can you give an example of how the existing text is inaccurate or results in confusion? -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23040 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23039] File name restriction on Windows
Tim Golden added the comment: Agree with RDM: we're just passing the path through to the Windows API (on Windows). We don't generally carry out this kind of pre-emptive check. -- resolution: - not a bug stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23039 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23041] csv needs more quoting rules
New submission from Samwyse:
The csv module currently implements four quoting rules for dialects:
QUOTE_MINIMAL, QUOTE_ALL, QUOTE_NONNUMERIC and QUOTE_NONE. These rules treat
values of None the same as an empty string, i.e. by outputting two consecutive
quotes. I propose the addition of two new rules, QUOTE_NOTNULL and
QUOTE_STRINGS. The former behaves like QUOTE_ALL while the later behaves like
QUOTE_NONNUMERIC, except that in both cases values of None are output as an
empty field. Examples follow.
Current behavior (which will remain unchanged)
csv.register_dialect('quote_all', quoting=csv.QUOTE_ALL)
csv.writer(sys.stdout, dialect='quote_all').writerow(['foo', None, 42])
foo,,42
csv.register_dialect('quote_nonnumeric', quoting=csv.QUOTE_NONNUMERIC)
csv.writer(sys.stdout, dialect='quote_nonnumeric').writerow(['foo', None,
42])
foo,,42
Proposed behavior
csv.register_dialect('quote_notnull', quoting=csv.QUOTE_NOTNULL)
csv.writer(sys.stdout, dialect='quote_notnull').writerow(['foo', None, 42])
foo,,42
csv.register_dialect('quote_strings', quoting=csv.QUOTE_STRINGS)
csv.writer(sys.stdout, dialect='quote_strings').writerow(['foo', None, 42])
foo,,42
--
components: Library (Lib)
messages: 232560
nosy: samwyse
priority: normal
severity: normal
status: open
title: csv needs more quoting rules
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23041
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23041] csv needs more quoting rules
R. David Murray added the comment: As an enhancement, this could be added only to 3.5. The proposal sounds reasonable to me. -- keywords: +easy nosy: +r.david.murray stage: - needs patch versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23041 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9536] defaultdict doc makes incorrect reference to __missing__ method
Changes by Berker Peksag berker.pek...@gmail.com: -- stage: needs patch - resolved ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9536 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23014] Don't have importlib.abc.Loader.create_module() be optional
Brett Cannon added the comment: Here is a patch that makes sure that if exec_module() is defined then so is create_module(). There really isn't any benefit in the code now, but starting in Python 3.6 we can make a very clear code path delineation between spec-based loading and old-fashioned load_module() instead of the current solution we have now where create_module() is used for either path and everything is intertwined. -- keywords: +patch stage: test needed - patch review Added file: http://bugs.python.org/file37427/require_create_module.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23014 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23013] Tweak wording for importlib.util.LazyLoader in regards to Loader.create_module()
Changes by Brett Cannon br...@python.org: -- dependencies: +Don't have importlib.abc.Loader.create_module() be optional ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23013 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23041] csv needs more quoting rules
Samwyse added the comment:
David: That's not a problem for me.
Sorry I can't provide real patches, but I'm not in a position to compile (much
less test) the C implementation of _csv. I've looked at the code online and
below are the changes that I think need to be made. My use cases don't require
special handing when reading empty fields, so the only changes I've made are to
the code for writers. I did verify that the reader code mostly only checks for
QUOTE_NOTNULL when parsing. This means that completely empty fields will
continue to load as zero-length strings, not None. I won't stand in the way of
anyone wanting to fix that for these new rules.
typedef enum {
QUOTE_MINIMAL, QUOTE_ALL, QUOTE_NONNUMERIC, QUOTE_NONE,
QUOTE_STRINGS, QUOTE_NOTNULL
} QuoteStyle;
static StyleDesc quote_styles[] = {
{ QUOTE_MINIMAL,QUOTE_MINIMAL },
{ QUOTE_ALL,QUOTE_ALL },
{ QUOTE_NONNUMERIC, QUOTE_NONNUMERIC },
{ QUOTE_NONE, QUOTE_NONE },
{ QUOTE_STRINGS,QUOTE_STRINGS },
{ QUOTE_NOTNULL,QUOTE_NOTNULL },
{ 0 }
};
switch (dialect-quoting) {
case QUOTE_NONNUMERIC:
quoted = !PyNumber_Check(field);
break;
case QUOTE_ALL:
quoted = 1;
break;
case QUOTE_STRINGS:
quoted = PyString_Check(field);
break;
case QUOTE_NOTNULL:
quoted = field != Py_None;
break;
default:
quoted = 0;
break;
}
csv.QUOTE_MINIMAL means only when required, for example, when a\n
field contains either the quotechar or the delimiter\n
csv.QUOTE_ALL means that quotes are always placed around fields.\n
csv.QUOTE_NONNUMERIC means that quotes are always placed around\n
fields which do not parse as integers or floating point\n
numbers.\n
csv.QUOTE_STRINGS means that quotes are always placed around\n
fields which are strings. Note that the Python value None\n
is not a string.\n
csv.QUOTE_NOTNULL means that quotes are only placed around fields\n
that are not the Python value None.\n
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23041
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23013] Tweak wording for importlib.util.LazyLoader in regards to Loader.create_module()
Brett Cannon added the comment: Fix is part of issue #23014, so if that goes in then this will be fixed as a side-effect. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23013 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23040] Better documentation for the urlencode safe parameter
Wojtek Ruszczewski added the comment:
I was looking at the sentence:
When query parameter is a str, the safe, encoding and error parameters are
passed down to quote_plus() for encoding.
The query argument can't be a string itself (gives a TypeError with 3.5a0 and I
think it's only intended to accept dicts or sequences of 2-tuples). The
parameter then must refer to a component of the query -- a key or a value.
The safe argument is passed down and is effective no matter if a component is
of str or bytes type (or a sequence with doseq), for example:
urlencode({b'/ n': ''}, safe='/')
'/+n='
(note the b; without safe the slash would get encoded as %2F).
Maybe it would also be good to change query parameter to query component in
that sentence.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23040
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21581] Consider dropping importlib.abc.Loader.create_module()
Brett Cannon added the comment: Issue #23014 is planning to make create_module() required so that module creation doesn't have a two-tiered way of specifying a default module (which is handy in C code). -- dependencies: +Don't have importlib.abc.Loader.create_module() be optional ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21581 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21581] Consider dropping importlib.abc.Loader.create_module()
Changes by Brett Cannon br...@python.org: -- assignee: - brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21581 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21099] Switch applicable importlib tests to use PEP 451 API
Brett Cannon added the comment: Should this be closed, Eric? -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21099 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19711] add test for changed portions after reloading a namespace package
Brett Cannon added the comment: Do we still need this patch, Eric? -- status: open - pending versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19711 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19698] Implement _imp.exec_builtin and exec_dynamic
Brett Cannon added the comment: I would still like to get this solved for Python 3.5. Should we hash out a solution at PyCon? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19698 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22919] Update PCBuild for VS 2015
Roundup Robot added the comment: New changeset 5754f069b123 by Steve Dower in branch 'default': Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release. https://hg.python.org/cpython/rev/5754f069b123 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22919 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22919] Update PCBuild for VS 2015
Steve Dower added the comment: I'll be closely tracking any issues that arise out of this throughout the next couple of days, but it should be fairly smooth (especially for people who don't upgrade VS immediately). There are certainly a few things that are broken, but I'll make separate issues for those. -- resolution: - fixed stage: patch review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22919 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9647] os.confstr() does not handle value changing length between calls
David Watson added the comment:
Here are the alternative patches to allow more than two calls to
confstr(). One patch set just keeps reallocating the buffer
until it's big enough, while the other makes a limited number of
attempts (in this case 20) before raising RuntimeError.
--
keywords: +patch
Added file: http://bugs.python.org/file37428/confstr-realloc-endless-2.7.diff
Added file: http://bugs.python.org/file37429/confstr-realloc-endless-3.4.diff
Added file: http://bugs.python.org/file37430/confstr-realloc-endless-3.5.diff
Added file: http://bugs.python.org/file37431/confstr-realloc-limited-2.7.diff
Added file: http://bugs.python.org/file37432/confstr-realloc-limited-3.4.diff
Added file: http://bugs.python.org/file37433/confstr-realloc-limited-3.5.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9647
___# HG changeset patch
# Parent 1edff7001f589dffaf8de4aebcb65a1f1d7deb5c
diff --git a/Modules/posixmodule.c b/Modules/posixmodule.c
--- a/Modules/posixmodule.c
+++ b/Modules/posixmodule.c
@@ -7936,12 +7936,24 @@ posix_confstr(PyObject *self, PyObject *
PyObject *result = NULL;
int name;
char buffer[256];
+char *recvbuf = buffer;
+char *allocated = NULL;
+size_t buflen = sizeof(buffer);
+size_t len;
if (PyArg_ParseTuple(args, O:confstr, conv_confstr_confname, name)) {
-int len;
-
-errno = 0;
-len = confstr(name, buffer, sizeof(buffer));
+
+/* Reset errno before each call as we may need to check it afterwards */
+while (errno = 0, (len = confstr(name, recvbuf, buflen)) buflen) {
+recvbuf = PyMem_Realloc(allocated, len);
+if (recvbuf == NULL) {
+PyErr_NoMemory();
+goto finally;
+}
+allocated = recvbuf;
+buflen = len;
+}
+
if (len == 0) {
if (errno) {
posix_error();
@@ -7952,15 +7964,11 @@ posix_confstr(PyObject *self, PyObject *
}
}
else {
-if ((unsigned int)len = sizeof(buffer)) {
-result = PyString_FromStringAndSize(NULL, len-1);
-if (result != NULL)
-confstr(name, PyString_AS_STRING(result), len);
-}
-else
-result = PyString_FromStringAndSize(buffer, len-1);
-}
-}
+result = PyString_FromStringAndSize(recvbuf, len-1);
+}
+}
+finally:
+PyMem_Free(allocated);
return result;
}
#endif
# HG changeset patch
# Parent aba5f771f5ec9e4004c0375ab4302f246a04bae7
diff --git a/Modules/posixmodule.c b/Modules/posixmodule.c
--- a/Modules/posixmodule.c
+++ b/Modules/posixmodule.c
@@ -9727,33 +9727,38 @@ posix_confstr(PyObject *self, PyObject *
PyObject *result = NULL;
int name;
char buffer[255];
+char *recvbuf = buffer;
+char *allocated = NULL;
+size_t buflen = sizeof(buffer);
size_t len;
if (!PyArg_ParseTuple(args, O:confstr, conv_confstr_confname, name))
return NULL;
-errno = 0;
-len = confstr(name, buffer, sizeof(buffer));
+/* Reset errno before each call as we may need to check it afterwards */
+while (errno = 0, (len = confstr(name, recvbuf, buflen)) buflen) {
+recvbuf = PyMem_Realloc(allocated, len);
+if (recvbuf == NULL) {
+PyErr_NoMemory();
+goto finally;
+}
+allocated = recvbuf;
+buflen = len;
+}
+
if (len == 0) {
if (errno) {
posix_error();
-return NULL;
}
else {
-Py_RETURN_NONE;
-}
-}
-
-if (len = sizeof(buffer)) {
-char *buf = PyMem_Malloc(len);
-if (buf == NULL)
-return PyErr_NoMemory();
-confstr(name, buf, len);
-result = PyUnicode_DecodeFSDefaultAndSize(buf, len-1);
-PyMem_Free(buf);
+result = Py_None;
+Py_INCREF(Py_None);
+}
}
else
-result = PyUnicode_DecodeFSDefaultAndSize(buffer, len-1);
+result = PyUnicode_DecodeFSDefaultAndSize(recvbuf, len-1);
+finally:
+PyMem_Free(allocated);
return result;
}
#endif
# HG changeset patch
# Parent 5754f069b12342acb69dff739782416092522748
diff --git a/Modules/posixmodule.c b/Modules/posixmodule.c
--- a/Modules/posixmodule.c
+++ b/Modules/posixmodule.c
@@ -14372,32 +14372,35 @@ os_confstr_impl(PyModuleDef *module, int
{
PyObject *result = NULL;
char buffer[255];
+char *recvbuf = buffer;
+char *allocated = NULL;
+size_t buflen = sizeof(buffer);
size_t len;
-errno = 0;
-len = confstr(name, buffer, sizeof(buffer));
+/* Reset errno before each call as we may need to check it afterwards */
+while (errno = 0, (len = confstr(name, recvbuf, buflen)) buflen) {
+recvbuf = PyMem_Realloc(allocated, len);
+if (recvbuf == NULL) {
+PyErr_NoMemory();
+goto finally;
+}
+allocated =
[issue22735] Fix various crashes exposed through mro() customization
Eldar Abusalimov added the comment: ping? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22735 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23042] Python 2.7.9 ctypes module doesn't build on FreeBSD x86
New submission from Marc-Andre Lemburg: With Python 2.7.8, ctypes builds fine on FreeBSD x86, but with Python 2.7.9, the build fails with: *** WARNING: renaming _ctypes since importing it failed: build/lib.freebsd-8.3-RELEASE-p3-i386-2.7/_ctypes.so: Undefined symbol ffi_call_win32 Since this is FreeBSD, there shouldn't really be any calls to ffi_call_win32() in the _ctypes module or libffi. Looking at the code changes in libffi/src/x86/ffi.c, it looks as if some of the #ifdefs for X86_WIN64 and X86_WIN32 were mixed up, causing calls to the Windows function to be compiled on FreeBSD x86, without also compiling the function definition in the same file. -- components: Build, ctypes messages: 232574 nosy: lemburg priority: normal severity: normal status: open title: Python 2.7.9 ctypes module doesn't build on FreeBSD x86 versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23042 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23042] Python 2.7.9 ctypes module doesn't build on FreeBSD x86
Marc-Andre Lemburg added the comment:
The cause seems to be these changes of the file (diff between the 2.7.8 and
2.7.9 version):
@@ -368,14 +374,21 @@ void ffi_call(ffi_cif *cif, void (*fn)(v
#ifdef X86_WIN64
case FFI_WIN64:
ffi_call_win64(ffi_prep_args, ecif, cif-bytes,
cif-flags, ecif.rvalue, fn);
break;
-#elif defined(X86_WIN32)
+#else
+#ifndef X86_WIN32
+case FFI_SYSV:
+ ffi_call_SYSV(ffi_prep_args, ecif, cif-bytes, cif-flags, ecif.rvalue,
+fn);
+ break;
+#else
case FFI_SYSV:
-case FFI_STDCALL:
case FFI_MS_CDECL:
+#endif
+case FFI_STDCALL:
ffi_call_win32(ffi_prep_args, ecif, cif-abi, cif-bytes, cif-flags,
ecif.rvalue, fn);
break;
case FFI_THISCALL:
case FFI_FASTCALL:
@@ -404,15 +417,10 @@ void ffi_call(ffi_cif *cif, void (*fn)(v
abi = FFI_STDCALL;
ffi_call_win32(ffi_prep_args, ecif, abi, cif-bytes, cif-flags,
ecif.rvalue, fn);
}
break;
-#else
-case FFI_SYSV:
- ffi_call_SYSV(ffi_prep_args, ecif, cif-bytes, cif-flags, ecif.rvalue,
-fn);
- break;
#endif
default:
FFI_ASSERT(0);
break;
}
@@ -785,14 +797,21 @@ ffi_raw_call(ffi_cif *cif, void (*fn)(vo
ecif.rvalue = rvalue;
switch (cif-abi)
{
-#ifdef X86_WIN32
+#ifndef X86_WIN32
+case FFI_SYSV:
+ ffi_call_SYSV(ffi_prep_args_raw, ecif, cif-bytes, cif-flags,
+ecif.rvalue, fn);
+ break;
+#else
case FFI_SYSV:
-case FFI_STDCALL:
case FFI_MS_CDECL:
+#endif
+#ifndef X86_WIN64
+case FFI_STDCALL:
ffi_call_win32(ffi_prep_args_raw, ecif, cif-abi, cif-bytes,
cif-flags,
ecif.rvalue, fn);
break;
case FFI_THISCALL:
case FFI_FASTCALL:
@@ -821,15 +840,10 @@ ffi_raw_call(ffi_cif *cif, void (*fn)(vo
cif-abi = abi = FFI_STDCALL;
ffi_call_win32(ffi_prep_args_raw, ecif, abi, cif-bytes, cif-flags,
ecif.rvalue, fn);
}
break;
-#else
-case FFI_SYSV:
- ffi_call_SYSV(ffi_prep_args_raw, ecif, cif-bytes, cif-flags,
-ecif.rvalue, fn);
- break;
#endif
default:
FFI_ASSERT(0);
break;
}
If neither X86_WIN64 nor X86_WIN32 are defined, the #ifndefs cause the
functions calls to be compiled in.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23042
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23040] Better documentation for the urlencode safe parameter
R. David Murray added the comment: OK, now I understand. How about this phrasing: The *safe*, *encoding*, and *error* parameters are passed down to :func:`quote_plus` (the *encoding* and *error* parameters are only passed when the query element is a :class:`str`). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23040 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23043] doctest ignores from __future__ import print_function
New submission from Vjacheslav: from __future__ import print_function print (1,2) 1 2 in interactive session, but, with this 3 lines in tmp.txt: python -m doctest tmp.txt fails (prints tuple) -- components: Library (Lib) messages: 232577 nosy: fva priority: normal severity: normal status: open title: doctest ignores from __future__ import print_function type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23043 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Arfrever Frehtes Taifersar Arahesis added the comment: It should not be more complex to read a line from a command line argument than to read a line from a regular file. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23040] Better documentation for the urlencode safe parameter
Wojtek Ruszczewski added the comment: Thanks, that's right and better, as it doesn't replicate the safe explanation. I've just noticed another small one, the docstring for quote() [2] says: encoding must not be specified if string is a str -- that should be ... is a bytes. [2] https://hg.python.org/cpython/file/default/Lib/urllib/parse.py#l690 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23040 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22823] Use set literals instead of creating a set from a list
Benjamin Peterson added the comment: 2to3 patch lgtm. Please apply to 3.4, too, though. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22823 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23011] Duplicate Paragraph in documentation for json module
Terry J. Reedy added the comment: The section documents JSONDecoder and then JSONEncoder. Looking at the current 3.4 online docs, I do not see any significant duplication within either entry. Even if there were duplication between, we might leave it to keep the entries complete in themselves. But not seeing any, this is moot. -- nosy: +terry.reedy versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23011 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Terry J. Reedy added the comment: Code entered with -c seems to be treated the same as code entered at the prompt of the interactive interpreter. 1/0 Traceback (most recent call last): File stdin, line 1, in module ZeroDivisionError: division by zero In both cases, the offending code is right there to be seen, so I can understand reluctance to echo it. For SyntaxErrors (and only them) echoing the code is needed to have something to point to. Idle's Shell does what you want. 1/0 Traceback (most recent call last): File pyshell#12, line 1, in module 1/0 ZeroDivisionError: division by zero Shell can do this because it has easy, platform-independent access to the tkinter Text widget storing and displaying previously entered code. I presume accessing a system-dependent console history buffer is much harder. Where the difference really matters is when the error is in previously defined objects. def f(): ... return a f() Traceback (most recent call last): File stdin, line 1, in module File stdin, line 2, in f NameError: name 'a' is not defined versus (Shell) def f(): return a f() Traceback (most recent call last): File pyshell#16, line 1, in module f() File pyshell#15, line 2, in f return a NameError: name 'a' is not defined -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Arfrever Frehtes Taifersar Arahesis added the comment: Argument of -c option can have multiple lines, while only 1 line can be directly entered in interactive interpreter. python -c $'line1\nline2\nline3\nline4\n...' -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18373] implement sys.get/setbyteswarningflag()
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18373 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18679] include a codec to handle escaping only control characters but not any others
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18679 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5166] ElementTree and minidom don't prevent creation of not well-formed XML
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5166 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Terry J. Reedy added the comment: One can paste multiple lines, comprising multiple statements, into the console interprer. (Shell only recognizes a single pasted statement.) I agree, however, that it seems that Python could keep the split version of the input line for the purpose of tracebacks. I just tried C:\Users\Terrypython -c import sys; print(sys.argv) ['-c'] I expected to see to see a list of 3 strings, not 1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23035] python -c: Line causing exception not shown for exceptions other than SyntaxErrors
Arfrever Frehtes Taifersar Arahesis added the comment: Arguments after argument of -c option are included in sys.argv: $ python -c import sys; print(sys.argv) a b ['-c', 'a', 'b'] -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23035 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23044] incorrect addition of floating point numbers
New submission from Bart Grzybicki: Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 Type help, copyright, credits or license for more information. 115.26 + 2.01 117.270001 115.26 + 2.02 117.28 115.27 + 2.01 117.28 -- messages: 232586 nosy: bartgee priority: normal severity: normal status: open title: incorrect addition of floating point numbers type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23044] incorrect addition of floating point numbers
Benjamin Peterson added the comment: Welcome to base 2. https://docs.python.org/2/tutorial/floatingpoint.html -- nosy: +benjamin.peterson resolution: - not a bug status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21793] httplib client/server status refactor
Demian Brecht added the comment: Updated patch addressing further reviews -- Added file: http://bugs.python.org/file37434/issue21793_6.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21793 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23004] mock_open() should allow reading binary data
Aaron Hill added the comment: I've created a patch that fixes this, and added an accompanying unit test (which fails without the change). -- keywords: +patch nosy: +Aaron1011 Added file: http://bugs.python.org/file37435/mock-open-allow-binary-data.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23004 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21279] str.translate documentation incomplete
Martin Panter added the comment: Update patch with typo fixed, removed note about the “codecs” module (which I never found useful either), and updated the doc string with similar wording. Terry, do you think the wording in the patch is good enough, or do you think some of your proposed wording should be included? -- Added file: http://bugs.python.org/file37436/issue21279.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21279 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23017] string.printable.isprintable() returns False
Changes by Steven D'Aprano steve+pyt...@pearwood.info: -- nosy: +steven.daprano ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23017 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23004] mock_open() should allow reading binary data
Demian Brecht added the comment:
Thanks for the patch Aaron. Unfortunately this doesn't quite fix the issue.
There are two problems with the patch:
If a bytes object is passed into mock_open, I'd expect a bytes object in the
output. In your patch, not only is this not the case (the output is a string
object), but the bytes object is being coerced into its string representation
in the resulting list. For example (simplified from your patch):
data = b'foo\nbar'
newline = b'\n'
['{}\n'.format(l) for l in data.split(newline)]
[b'foo'\n, b'bar'\n]
What I would expect to see in this case is:
[b'foo\n', b'bar\n']
--
nosy: +demian.brecht
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23004
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23004] mock_open() should allow reading binary data
Demian Brecht added the comment: There are two problems with the patch That was intended to be removed after I changed the wording :P -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23004 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22979] Use of None in min and max
Steven D'Aprano added the comment: Even though I agree with closing this issue, there is some support for ignoring certain missing values when calculating min() and max(). The draft 2008 revision of IEEE-754 includes two functions maxNum and minNum which silently skip over NANs: https://en.wikipedia.org/wiki/IEEE_754_revision#min_and_max The R language also supports max and min skipping over missing values: https://stat.ethz.ch/R-manual/R-devel/library/base/html/Extremes.html The problem is that there are so many different things which somebody might want to do, it is hard to tell which (if any) the built-ins should support: - silently skip over None - or NANs - or treat some other, user-specified, value as missing - treat None as the smallest (or largest) value - treat the presence of None as an error - etc. I think that min() and max() should continue to be relatively simple-minded and let users write their own more complex versions if needed, e.g. by calling min(filter(condition, values)). -- nosy: +steven.daprano ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22979 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23045] json data iteration through loop in python
Changes by vegeshna satyanarayana raju satya.nani...@gmail.com: -- nosy: satyanani40 priority: normal severity: normal status: open title: json data iteration through loop in python ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23045 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23045] json data iteration through loop in python
New submission from vegeshna satyanarayana raju:
I have json data in following format
{message:[frappe,websocerp,erpnext]}
I want each name (frappe, websocerp, erpnext) in three iteration
after that i can use as
frappe.something.get_data()
websocerp.something.get_data()
erpnext.something.get_data()
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23045
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23045] json data iteration through loop in python
Steven D'Aprano added the comment: This is a bug tracker for issues in the Python language and standard library, not a service for learning how to program using Python. If you have an actual bug to report, you should give more detail including the actual code you used, the result you expected, and the result you actually got. Otherwise you should try asking your question on the python-l...@python.org mailing list, the comp.lang.python newsgroup, /r/python on Reddit, StackOverflow, or one of the many other public forums for discussing Python programming issues. -- nosy: +steven.daprano resolution: - not a bug status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23045 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23043] doctest ignores from __future__ import print_function
Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23043 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23041] csv needs more quoting rules
Raymond Hettinger added the comment: Samwyse, are these suggestions just based on ideas of what could be done or have you encountered real-world CSV data exchanges that couldn't be handled by the CSV module? -- assignee: - skip.montanaro nosy: +rhettinger, skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23041 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22875] asyncio: call_soon() documentation unclear on timing
Martin Panter added the comment: I have been bitten by this when attempting to implement my own event loops. Parts of the “asyncio” code itself expects that the callback is not invoked directly after call_soon() returns. Here is a simple patch. -- keywords: +patch nosy: +vadmium versions: +Python 3.4 Added file: http://bugs.python.org/file37437/call_soon.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22875 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23046] asyncio.BaseEventLoop is documented, but only exported via asyncio.base_events
New submission from Martin Panter: The documentation mentions BaseEventLoop as an attribute of the “asyncio” module, but it is not actually there (at least in v3.4.2). I have to import it specially from “asyncio.base_events”. Is this an oversight in the documentation, or am I relying on undocumented internals? I find the BaseEventLoop class is somewhat helpful for implementing my own event loops. -- components: asyncio messages: 232598 nosy: gvanrossum, haypo, vadmium, yselivanov priority: normal severity: normal status: open title: asyncio.BaseEventLoop is documented, but only exported via asyncio.base_events versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23046 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
