[issue46070] _PyImport_FixupExtensionObject() regression causing a crash in subintepreters

Change by Manuel Reimer : -- nosy: +M-Reimer ___ Python tracker <https://bugs.python.org/issue46070> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45523] Python3 ThreadingHTTPServer fails to send chunked encoded response

New submission from Manuel : I'm implementing an HTTPServer class that produces a response with transfer-encoding chunked mode. I'm sending the chunks as described in https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding#chunked_encoding If I send chunks of l

[issue41631] _ast module: get_global_ast_state() doesn't work with Mercurial lazy import

Manuel Jacob added the comment: I was running "make all" and I also ran the documentation generator command without an error. However, I tried it again and now it failed the same way as reported. With a debug build, I get "Python/Python-ast.c:231: get_ast_state: Assertion

[issue41631] _ast module: get_global_ast_state() doesn't work with Mercurial lazy import

Manuel Jacob added the comment: I couldn’t reproduce the problem with a freshly compiled Python 3.9.0rc1 on Arch Linux. Was this ever reproduced on a non-Red Hat system? -- nosy: +mjacob ___ Python tracker <https://bugs.python.org/issue41

[issue33660] pathlib.Path.resolve() returns path with double slash when resolving a relative path in root directory

Manuel Barkhau added the comment: This issue cropped up recently in the black project: https://github.com/psf/black/issues/1631 It appears to me that PR 7666 was closed without being merged. I created https://github.com/python/cpython/pull/21971 before I had found this issue

[issue33660] pathlib.Path.resolve() returns path with double slash when resolving a relative path in root directory

Change by Manuel Barkhau : -- nosy: +mbarkhau nosy_count: 6.0 -> 7.0 pull_requests: +21079 pull_request: https://github.com/python/cpython/pull/21971 ___ Python tracker <https://bugs.python.org/issu

[issue41221] Output of print() might get truncated in unbuffered mode

Manuel Jacob added the comment: It’s possible to trigger the problem on Unix with much smaller sizes, e.g. by interrupting the write() with a signal handler (even if the signal handler doesn’t do anything). The following script starts a subprocess doing a 16MiB write and sends a signal

[issue41221] Output of print() might get truncated in unbuffered mode

Manuel Jacob added the comment: `io.TextIOWrapper.write()` returns the length of the passed string instead of the actually written number of characters. % python -u -c "import sys; print(sys.stdout.write('x'*4294967296), file=sys.stderr)" | wc -c 4294967296 2147479552

[issue41221] Output of print() might get truncated in unbuffered mode

Manuel Jacob added the comment: 2147479552 is the 0x7000 bytes limit documented for write() on Linux (source: https://man7.org/linux/man-pages/man2/write.2.html). The limit could be even smaller in other circumstances or other systems. I’m adding Victor Stinner to the nosy list, as he

[issue41221] Output of print() might get truncated in unbuffered mode

New submission from Manuel Jacob : Without unbuffered mode, it works as expected: % python -c "import sys; sys.stdout.write('x'*4294967296)" | wc -c 4294967296 % python -c "import sys; print('x'*4294967296)" | wc -c 4294967297 With unbuffered

[issue41091] Remove recommendation in curses module documentation to initialize LC_ALL and encode strings

Change by Manuel Jacob : -- keywords: +patch pull_requests: +20319 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21159 ___ Python tracker <https://bugs.python.org/issu

[issue41091] Remove recommendation in curses module documentation to initialize LC_ALL and encode strings

New submission from Manuel Jacob : The documentation for the curses module (https://docs.python.org/3.9/library/curses.html) has the following note: > Since version 5.4, the ncurses library decides how to interpret non-ASCII > data using the nl_langinfo function. That means that you h

[issue41051] Flush file after warning is written

Change by Manuel Jacob : -- keywords: +patch pull_requests: +20175 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21000 ___ Python tracker <https://bugs.python.org/issu

[issue41051] Flush file after warning is written

New submission from Manuel Jacob : Calling warnings.warn() will write to a file, but not flush it. On Python 3.9+, it won’t usually be a problem because the file is most likely stderr, which is always line-buffered. However, on older Python versions or if a different file is used, the current

[issue17110] sys.argv docs should explaining how to handle encoding issues

Manuel Jacob added the comment: If the encoding supports it, since which Python version do Py_DecodeLocale() and os.fsencode() roundtrip? The background of my question is that Mercurial goes some extra rounds to determine the correct encoding to emulate what Py_EncodeLocale() would do

[issue41012] Some code comments refer to removed initfsencoding()

New submission from Manuel Jacob : Some code comments refer to initfsencoding(), which was however removed after Python 3.7. -- messages: 371779 nosy: mjacob priority: normal severity: normal status: open title: Some code comments refer to removed initfsencoding

[issue17110] sys.argv docs should explaining how to handle encoding issues

Manuel Jacob added the comment: The actual startup code uses Py_DecodeLocale() for converting argv from bytes to unicode. Since which Python version is it guaranteed that Py_DecodeLocale() and os.fsencode() roundtrip? -- nosy: +mjacob ___ Python

[issue40983] urllib.request.url2pathname() unconditionally uses utf-8 encoding and "replace" error handler

Manuel Jacob added the comment: I’ve created issue40996, which suggests that urllib should fsdecode percent-encoded parts of file URIs on Unix. Since the two tickets are very related and I’d prefer if the issue was solved more generally for the whole module, I close this as a duplicate

[issue40996] urllib should fsdecode percent-encoded parts of file URIs on Unix

New submission from Manuel Jacob : On Unix, file names are bytes. Python mostly prefers to use unicode for file names. On the Python <-> system boundary, os.fsencode() / os.fsdecode() are used. In URIs, bytes can be percent-encoded. On Unix, most applications pass the percent-decoded

[issue40983] urllib.request.url2pathname() unconditionally uses utf-8 encoding and "replace" error handler

Change by Manuel Jacob : -- title: Can’t configure encoding used by urllib.request.url2pathname() -> urllib.request.url2pathname() unconditionally uses utf-8 encoding and "replace" error handler ___ Python tracker <https:/

[issue40983] Can’t configure encoding used by urllib.request.url2pathname()

New submission from Manuel Jacob : On Python 2, it was possible to recover a percent-encoded byte: >>> from urllib import url2pathname >>> url2pathname('%ff') '\xff' On Python 3, the byte is decoded using the utf-8 encoding and the "replace" er

[issue39229] library/functions.rst causes translated builds to fail

Manuel Kaufmann added the comment: We are having a similar issue in python-docs-es translation. cpython/Doc/library/ctypes.rst:: WARNING: inconsistent term references in translated message. original: [], translated: [':ref:`evento de auditoría `'] https://travis-ci.org/github/pyt

[issue40868] io.TextIOBase.buffer is not necessarily a buffer

New submission from Manuel Jacob : https://docs.python.org/dev/library/io.html#io.TextIOBase.buffer says: "The underlying binary buffer (a BufferedIOBase instance) that TextIOBase deals with. This is not part of the TextIOBase API and may not exist in some implementations."

[issue40457] Python fails to compile/load _ssl module if OpenSSL is compiled with no-tls1-method

Manuel Jacob added the comment: For the record, I’ve added a comment to the pull request about that ssl.PROTOCOL_TLSv1_1 / ssl.PROTOCOL_TLSv1_2 are now defined unconditionally. https://github.com/python/cpython/commit/6e8cda91d92da72800d891b2fc2073ecbc134d98#r39569316 -- nosy

[issue39464] Allow translating argument error messages

New submission from José Manuel Ferrer : Argument error messages display the untranslatable text 'argument ', which should be translatable to other languages, just like it's possible to do with the rest of the constructed error message. -- components: Library (Lib) m

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Manuel Barkhau added the comment: > If you pass a string, you will get a string, so existing code will continue > to work as before. Somebody might have code that is running against a flat directory and have written their ignore function expecting to get a pathlib.Path, because that&

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Manuel Barkhau added the comment: > For completeness, a similar problem is present also on python < 3.8 Fair point. I'll have a look. -- ___ Python tracker <https://bugs.python.

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Change by Manuel Barkhau : -- pull_requests: +17554 pull_request: https://github.com/python/cpython/pull/18168 ___ Python tracker <https://bugs.python.org/issue39

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Change by Manuel Barkhau : -- pull_requests: +17509 pull_request: https://github.com/python/cpython/pull/18122 ___ Python tracker <https://bugs.python.org/issue39

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Manuel Barkhau added the comment: Unless somebody else wants to, I could have a go at an PR to update shutil.py -- ___ Python tracker <https://bugs.python.org/issue39

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Manuel Barkhau added the comment: Is there anything I can do to help move this forward? -- ___ Python tracker <https://bugs.python.org/issue39390> ___ ___ Pytho

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Manuel Barkhau added the comment: > This looks like a backward incompatible change in 3.8. Indeed. > Should not copytree convert arguments of the ignore callback to str and list > correspondingly? Well, since any existing code probably expects that behavior (or at least probably

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Change by Manuel Barkhau : -- keywords: +patch pull_requests: +17462 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18069 ___ Python tracker <https://bugs.python.org/issu

[issue39390] shutil.copytree - 3.8 changed argument types of the ignore callback

Change by Manuel Barkhau : -- title: shutil.copytree - ignore callback behaviour change -> shutil.copytree - 3.8 changed argument types of the ignore callback ___ Python tracker <https://bugs.python.org/issu

[issue39390] shutil.copytree - ignore callback behaviour change

New submission from Manuel Barkhau : In Python 3.8, the types of the parameters to the ignore callable appear to have changed. Previously the `src` parameter was a string and the `names` parameter was a list of strings. Now the `src` parameter appears to be either a `pathlib.Path` or an

[issue38710] unsynchronized write pointer in io.TextIOWrapper in 'r+' mode

New submission from Manuel Ignacio Pérez Alcolea : There seems to be a bug in the `io.TextIOWrapper` class while working in 'r+' mode, although I can't say the source of the problem is right there. The write pointer doesn't match `file.tell()` after performing a read ope

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Manuel Cerón : -- nosy: -ceronman ___ Python tracker <https://bugs.python.org/issue21879> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25737] array is not a Sequence

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue25737> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23864] issubclass without registration only works for "one-trick pony" collections ABCs.

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue23864> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35360] Update SQLite to 3.26 in Windows and macOS installer builds

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue35360> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue21879> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18299] Change script_helper to use universal_newlines=True in _assert_python

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue18299> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25026] (FreeBSD/OSX) Fix fcntl module to accept 'unsigned long' type commands for ioctl(2).

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue25026> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29446] Improve tkinter 'import *' situation

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker <https://bugs.python.org/issue29446> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34321] mmap.mmap() should not necessarily clone the file descriptor

New submission from Manuel : mmap.mmap(fileno, length, flags, prot, access, offset) always clones the file descriptor that should be used [1]. The cloning of the file descriptor seems to be done to ensure that the file cannot be closed behind mmap's back, but if you are mmap()'in

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

Manuel Vazquez Acosta added the comment: Correction, the documentation for CALL_FUNCTION_VAR said: Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The top element on the stack contains the variable argument list, followed by keyword and positional arguments. In a

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

Change by Manuel Vazquez Acosta : -- keywords: +patch pull_requests: +6075 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33216> ___ _

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

New submission from Manuel Vazquez Acosta : The documentation of the dis module says that: CALL_FUNCTION_VAR (argc) Calls a function. *argc* is interpreted as in CALL_FUNCTION. The top elements on the stack are the keyword arguments, followed by the variable argument list, and then

[issue33216] CALL_FUNCTION_VAR

Change by Manuel Vazquez Acosta : -- nosy: mvaled priority: normal severity: normal status: open title: CALL_FUNCTION_VAR ___ Python tracker <https://bugs.python.org/issue33

[issue31113] Stack overflow with large program

Manuel Krebber added the comment: @Serhiy That would require me to compile Python myself though, right? Is there a reason why the limit is only for try/for and not for if? @Antoine Well, the goal is to be able to generate Python 2 compatible code . I will try to split the code into more

[issue31113] Stack overflow with large program

Manuel Krebber added the comment: I have already tried to reduce the nesting, but it still crashes. I have to admit that ~20 levels of nesting are still quite a lot. But I am surprised that so few levels of nesting already are a problem for the parser... I have attached the generated code

[issue31113] Stack overflow with large program

Manuel Krebber added the comment: 1) Yes. 2) A .pyc file was not generated. 3) It is always the same location where the error occurs. 4) It did not crash on the linux machine that I tested it on. I have tried to split the code up into multiple files, but it still crashes. I have uploaded the

[issue31113] Stack overflow with large program

New submission from Manuel Krebber: With a pattern matching library I am generating some Python code that matches patterns. For a very big pattern set I generate a Python file which is about 20MB and has ~300K LOC. When I try to execute the file with Python 3.6.2 on Windows 10 (64bit), the

[issue29830] pyexpat.errors doesn't have __spec__ and __loader__ set

Manuel Jacob added the comment: You're of course right that pyexpat is an extension module and not a builtin module. I was confused because on PyPy it's a builtin module. But the same question applies for ExtensionFileLoader.is_package(). It returns False in the case of pyex

[issue29830] pyexpat.errors doesn't have __spec__ and __loader__ set

New submission from Manuel Jacob: The same applies to pyexpat.model. It seems like pyexpat is the only builtin module which has submodules (errors, model). Normally, as I understand it, the module gets imported given a spec and the import machinery ensures that this spec ends up in the

[issue29418] inspect.isroutine does not return True for some bound builtin methods

New submission from Manuel Krebber: Some of the builtin methods are not recognized as such by inspect.isroutine(). inspect.ismethoddescriptor() only returns True for the unbound versions of the methods but not the bound ones. For example: >>> inspect.isroutine(object.__st

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: One question I was wondering about is whether those types should be checked by inspect.isroutine() as well. -- ___ Python tracker <http://bugs.python.org/issue29

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: Okay, I added MethodDescriptorType to the types module and updated the docs. Hope this is okay now. -- Added file: http://bugs.python.org/file46455/slot-wrapper-types.patch ___ Python tracker <h

[issue26355] Emit major version based canonical URLs for docs

Manuel Krebber added the comment: Sorry, I accidentally replied to the worng issue -.- -- ___ Python tracker <http://bugs.python.org/issue26355> ___ ___ Python-bug

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: I created the last patch without commiting, so maybe this one will work properly with the revision tool. -- Added file: http://bugs.python.org/file46429/slot-wrapper-types.patch ___ Python tracker <h

[issue26355] Emit major version based canonical URLs for docs

Changes by Manuel Krebber : Removed file: http://bugs.python.org/file46428/slot-wrapper-types.patch ___ Python tracker <http://bugs.python.org/issue26355> ___ ___ Pytho

[issue26355] Emit major version based canonical URLs for docs

Manuel Krebber added the comment: I create the last diff without creating a commit, so maybe this one works better. -- nosy: +Wheerd Added file: http://bugs.python.org/file46428/slot-wrapper-types.patch ___ Python tracker <http://bugs.python.

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: Alright, I added some tests and tried it again with the patch. -- Added file: http://bugs.python.org/file46427/slot-wrapper-types.patch ___ Python tracker <http://bugs.python.org/issue29

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: I added some docs, but I am not sure what I would want to test here. There are no tests for types.BuiltinMethodType either. Maybe the string representation of it could be tested, but an isinstance test seems pretty redundant. I hope this patch file works

[issue29377] Add the 'wrapper_descriptor' type to the types module

Manuel Krebber added the comment: I would suggest the names SlotWrapperType and MethodWrapperType because I think they match their string representations the closest. For checking whether something is a method/function one could also use inspect.isroutine (or inspect.ismethoddescriptor), but

[issue29377] Add the 'wrapper_descriptor' type to the types module

Changes by Manuel Krebber : -- keywords: +patch Added file: http://bugs.python.org/file46420/0001-Added-SlotWrapperType-and-MethodWrapperType-to-the-t.patch ___ Python tracker <http://bugs.python.org/issue29

[issue29377] Add the 'wrapper_descriptor' type to the types module

New submission from Manuel Krebber: There currently is no type in the types module for the slot wrappers/wrapper_descriptor types. I would like to have something like WrapperDescriptor = type(object.__init__) added to it (or maybe even add it to MethodType). This would be helpful to

[issue28773] typing.FrozenSet missing in documentation.

Manuel Krebber added the comment: I updated the patch to add reflect the covariance. -- Added file: http://bugs.python.org/file45606/frozenset-doc.patch ___ Python tracker <http://bugs.python.org/issue28

[issue28773] typing.FrozenSet missing in documentation.

New submission from Manuel Krebber: The typing.FrozenSet is missing in the typing module documentation. I have attached a patch that adds it similar to the typing.Set which is already in the documentation. -- components: Library (Lib) files: frozenset-doc.patch keywords: patch

[issue28404] Logging SyslogHandler not appending '\n' to the end

José Manuel added the comment: Sorry to bother you again, but I've tested this not only with Fluentd, but with a RSYSLOG server and it does not work with TCP except if you manually add the trailer LF character. Other than that, UDP default transport protocol has no issues and works fine

[issue28404] Logging SyslogHandler not appending '\n' to the end

José Manuel added the comment: After reading the RFC5424 it seems that there is no such "new line message delimiter": 4.3.1. Message Length The message length is the octet count of the SYSLOG-MSG in the SYSLOG-FRAME. A transport receiver MU

[issue28404] Logging SyslogHandler not appending '\n' to the end

New submission from José Manuel: I'm using SyslogHandler from logging.handlers to send syslog messages to a Fluentd input (https://github.com/fluent/fluentd/blob/master/lib/fluent/plugin/in_syslog.rb), both in TCP and UDP. UDP works fine, but TCP does not work. The "problem&qu

[issue28296] Add __le__ and __ge__ to collections.Counter

Manuel Krebber added the comment: Oh, I should have searched properly before creating this ticket. Sorry about that. I guess I will be subclassing Counter in my project then, to get this functionality... Only problem is, that when using the builtin __add__ etc. of my Counter subclass, I will

[issue28296] Add __le__ and __ge__ to collections.Counter

New submission from Manuel Krebber: I would really like there to be comparison operators for collection.Counter similar to the ones for sets. While you can now use minus to some degree for that comparison, it is very inefficient. I have attached an implementation of __ge__ and __le__ as a

[issue27393] Command to activate venv in Windows has wrong path

New submission from Manuel Kaufmann: The `venv` module has a bug in the command to activate it on Windows. In 3.3 and 3.4 the bar used is wrong: `/` instead `\` * https://docs.python.org/3.4/library/venv.html#creating-virtual-environments * https://docs.python.org/3.3/library/venv.html

[issue26367] importlib.__import__ does not fail for invalid relative import

Manuel Jacob added the comment: I think the "What's New" entry has two typos. It should be `importlib.__import__()` instead of `importlib.__init__()` and SystemError instead of RuntimeError. -- ___ Python tracker <http

[issue26367] importlib.__import__ does not fail for invalid relative import

Manuel Jacob added the comment: Done. I'm a bit surprised this wasn't necessary for my previous two patches, but they were even more trival than this one. ;) Do we have to wait until my tracker profile is updated? -- ___ Python trac

[issue26367] importlib.__import__ does not fail for invalid relative import

Manuel Jacob added the comment: (For some reason, I forgot to submit the previous comment). The attached patches fix the issue (one for the 3.5 branch, one for the default branch) by bringing importlib.__import__ closer to the builtin __import__. The extra code in the default / 3.6 branch is

[issue26367] importlib.__import__ does not fail for invalid relative import

Changes by Manuel Jacob : Added file: http://bugs.python.org/file41938/relimport-3.6.patch ___ Python tracker <http://bugs.python.org/issue26367> ___ ___ Python-bug

[issue26367] importlib.__import__ does not fail for invalid relative import

Changes by Manuel Jacob : -- keywords: +patch Added file: http://bugs.python.org/file41937/relimport-3.5.patch ___ Python tracker <http://bugs.python.org/issue26

[issue26367] importlib.__import__ does not fail for invalid relative import

New submission from Manuel Jacob: Python 3.6.0a0 (default:6c6f7dff597b, Feb 16 2016, 01:24:51) [GCC 5.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import importlib >>> importlib.__import__(&#x

[issue23742] expandvars removes single quotes ( ' )

New submission from Manuel Vögele: When executing os.path.expandvars("%SystemDrive%\\Foo'Bar") the function erases the ' returning 'C:\\FooBar' using Python 3.4.3 on Windows 7 -- components: Library (Lib) messages: 238968 nosy: manuel_v, serhiy.storc

[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docos lie)

Manuel Jacob added the comment: Maybe I'm missing something, but it seems to me that test_int_subclass_with_index() is testing for the exactly wrong behaviour. Isn't the point of this issue that operator.index(a) should be equal to a.__index__()? Why are the tests checking tha

[issue1185124] pydoc doesn't find all module doc strings

Changes by Manuel Pégourié-Gonnard : -- nosy: -mpg ___ Python tracker <http://bugs.python.org/issue1185124> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17336] Complex number representation round-trip doesn't work with signed zero values

New submission from Manuel Jacob: When evaluating, signed zero complex numbers aren't recovered correctly. >>> -0j (-0-0j) >>> (-0-0j) 0j >>> 0j 0j According to http://docs.python.org/dev/reference/datamodel.html#object.__repr__ the representation can be use

[issue17223] Initializing array.array with unicode type code and buffer segfaults

Manuel Jacob added the comment: http://docs.python.org/3/library/array.html states that the 'u' type code is deprecated together with the rest of the Py_UNICODE API (which includes PyUnicode_FromUnicode), so keeping this using PyUnicode_FromUnicode shoul

[issue17275] io.BufferedWriter shows wrong type in argument error message

Manuel Jacob added the comment: Added a new patch including tests for the C implementations of BufferedWriter and BufferedRandom. -- Added file: http://bugs.python.org/file29164/issue17275_with_test.diff ___ Python tracker <http://bugs.python.

[issue17275] io.BufferedWriter shows wrong type in argument error message

Manuel Jacob added the comment: The attached patch fixes the issue. Should I write a test? -- keywords: +patch Added file: http://bugs.python.org/file29161/issue17275.diff ___ Python tracker <http://bugs.python.org/issue17

[issue17275] io.BufferedWriter shows wrong type in argument error message

New submission from Manuel Jacob: >>> import io >>> io.BufferedWriter(io.BytesIO(), 1024, 1024, 1024) Traceback (most recent call last): File "", line 1, in TypeError: BufferedReader() takes at most 2 arguments (4 given) It should be "BufferedWri

[issue17223] Initializing array.array with unicode type code and buffer segfaults

Manuel Jacob added the comment: I've attached a new patch with a test that segfaults on Python 3.3 and passes on hg tip with the patch applied. -- Added file: http://bugs.python.org/file29110/issue17223_with_test.diff ___ Python tracker

[issue17223] Initializing array.array with unicode type code and buffer segfaults

Manuel Jacob added the comment: The attached patch fixes the crash. Output: >>> from array import array >>> str(array('u', b'asdf')) Traceback (most recent call last): File "", line 1, in ValueError: character U+66647361 is not in range [U+00

[issue17223] Initializing array.array with unicode type code and buffer segfaults

New submission from Manuel Jacob: >>> from array import array >>> str(array('u', b'asdf')) [1]19411 segmentation fault (core dumped) python This error occures with Python 3.3 and hg tip but not with Python 3.2. -- components: Librar

[issue16144] misleading sentence in reference/import

New submission from Manuel Pégourié-Gonnard: I find the following sentences, from import.rst, section "Finders and loaders", misleading: "Python includes a number of default finders and importers. One knows how to locate frozen modules, and another knows how to locate built-i

[issue1185124] pydoc doesn't find all module doc strings

Changes by Manuel Pégourié-Gonnard : -- nosy: +mpg ___ Python tracker <http://bugs.python.org/issue1185124> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16080] test_decimal causes other tests to fail with LC_ALL=fr_FR

New submission from Manuel Pégourié-Gonnard: Some tests, namely test_email, test_locale and test_mailbox, normally pass, but fail if both of the following conditions are met: - the local is fr_FR (or probably any other non-C locale) - test_decimal is run before them Steps to repoduce

[issue15275] isinstance is called a more times that needed in ntpath

Manuel de la Pena added the comment: Tests indeed cover the changes made. I don't know about a decent way of doing benchmarks for the changes. Any recommendation? > If this patch is applied I think it would be good to change posixpath too. I agree and I'd love to do it but in

[issue15275] isinstance is called a more times that needed in ntpath

Changes by Manuel de la Pena : -- nosy: +brian.curtin ___ Python tracker <http://bugs.python.org/issue15275> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15286] normpath does not work with local literal paths

Manuel de la Pena added the comment: Antoine, What the MSDN is stating is that the Windows functions from COM will not normalize the path if it is prefixed by \\?\. That is, if a user wanted to do: path = r'\\?\C:\Users\mandel\..\Desktop\test' with open(path, 'w') as fd:

[issue15286] normpath does not work with local literal paths

New submission from Manuel de la Pena : Local literal paths are those paths that do use the \\?\ that allows to have paths longer that the MAX_PATH set by Windows (http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#short_vs._long_names). While UNC (http

[issue15275] isinstance is called a more times that needed in ntpath

Changes by Manuel de la Pena : Removed file: http://bugs.python.org/file26295/f5c57ba1124b.diff ___ Python tracker <http://bugs.python.org/issue15275> ___ ___ Python-bug

  1   2   >