[issue13627] Python SSL stack doesn't support Elliptic Curve ciphers

Changes by Antoine Pitrou : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue13627] Python SSL stack doesn't support Elliptic Curve ciphers

Antoine Pitrou added the comment: > Perhaps we should make these algorithms build conditional? Are these > patent issues of concern to us? Well, if RedHat used the "standard" OPENSSL_NO_ECDH flag, it's easy enough to fix compilation of the ssl module. -- _

[issue2382] [Py3k] SyntaxError cursor shifted if multibyte character is in line.

Petri Lehtinen added the comment: What's the status of this issue? FWIW, this is not only a problem with east asian characters: >>> ä äää File "", line 1 ä äää ^ SyntaxError: invalid syntax -- nosy: +petri.lehtinen versions: +Python 3.2, Python 3.3 -Python 3.0 _

[issue6321] Reload Python modules when running programs

Changes by Ned Deily : -- resolution: out of date -> duplicate stage: -> committed/rejected superseder: -> IDLE/Win Installer: drop -n switch for 2.7/3.1; install 3.1 as idle3 ___ Python tracker _

[issue4691] IDLE Code Caching Windows

Changes by Ned Deily : -- resolution: -> duplicate stage: needs patch -> committed/rejected status: open -> closed superseder: -> IDLE/Win Installer: drop -n switch for 2.7/3.1; install 3.1 as idle3 versions: +Python 2.7, Python 3.1 -Python 2.6 ___

[issue13644] Python 3 crashes (segfaults) with this code.

maniram maniram added the comment: Oops, to reproduce this bug after running the code run "recurse()". -- ___ Python tracker ___ ___

[issue13644] Python 3 crashes (segfaults) with this code.

maniram maniram added the comment: But Python 2 doesn't crash after running the code. -- ___ Python tracker ___ ___ Python-bugs-list

[issue13644] Python 3 crashes (segfaults) with this code.

Benjamin Peterson added the comment: Python isn't crashing; it's bailing out of an impossible situation. It's not clear what the correct behavior is, since you're basically preventing Python from aborting the recursive behavior. -- nosy: +benjamin.peterson ___

[issue13644] Python 3 crashes (segfaults) with this code.

Changes by maniram maniram : -- title: Python 3 crashes with this code. -> Python 3 crashes (segfaults) with this code. ___ Python tracker ___ __

[issue13644] Python 3 crashes with this code.

Changes by maniram maniram : -- title: Python crashes with this code. -> Python 3 crashes with this code. ___ Python tracker ___ ___ P

[issue13644] Python crashes with this code.

New submission from maniram maniram : When you run the following code, Python 3 (not Python 2) crashes. Interestingly, Python 2.7 doesn't seem to be affected and correctly raises an error about recursion ( so this must be a regression ). The code's recursion should be detected and Python should

[issue13627] Python SSL stack doesn't support Elliptic Curve ciphers

Meador Inge added the comment: ECC is *not* available in the OpenSSL package provided on RedHat systems. RedHat intentionally strips it due to patent concerns (http://en.wikipedia.org/wiki/ECC_patents). Therefore committing this work made it much more difficult to build the ssl module on Re

[issue8098] PyImport_ImportModuleNoBlock() may solve problems but causes others.

Changes by Eric Snow : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8098] PyImport_ImportModuleNoBlock() may solve problems but causes others.

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue13607] Move generator specific sections out of ceval.

Nick Coghlan added the comment: The thing that most appeals to me with this concept is moving closer to making it possible to experiment with generator-style functionality in *extension* modules (albeit extension modules that are coupled to private CPython APIs). So, for me, "not worse than t

[issue13607] Move generator specific sections out of ceval.

Meador Inge added the comment: With the new patch I see no benefits on the same micro-benchmarks you posted (it is even slower for the smaller case) on a quad-core 64-bit F15 box: BEFORE: $ ./python -mtimeit "def y(n):" " for x in range(n):" "yield x" "sum(y(10))" 100 loops, best o

[issue13607] Move generator specific sections out of ceval.

Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13643] 'ascii' is a bad filesystem default encoding

Antoine Pitrou added the comment: > The standard encoding is UTF-8. How so? I don't know of any Linux or Unix spec which says so. If you get the Linux heads to standardize this then I'll certainly be very happy (and countless others will, too). But AFAIK this it not the case and I don't see why

[issue13643] 'ascii' is a bad filesystem default encoding

Martin Pool added the comment: On 21 December 2011 12:16, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > So, you're complaining about something which works, kind of: > > $ touch héhé > $ LANG=C python3 -c "import os; print(os.listdir())" > ['h\udcc3\udca9h\udcc3\udca9'] It's

[issue13643] 'ascii' is a bad filesystem default encoding

Martin Pool added the comment: Thanks for the example. Like you say, realistically, all data exchanged with other programs and with the system needs to be in the same encoding. (User document content may be in something else.) On modern systems, this problem is solved by making the standard e

[issue13643] 'ascii' is a bad filesystem default encoding

Antoine Pitrou added the comment: So, you're complaining about something which works, kind of: $ touch héhé $ LANG=C python3 -c "import os; print(os.listdir())" ['h\udcc3\udca9h\udcc3\udca9'] > This makes robustly working with non-ascii filenames on different > platforms needlessly annoying, g

[issue13643] 'ascii' is a bad filesystem default encoding

Martin added the comment: > During 1 month, we had PYTHONFSENCODING environment variable. It was not a > good idea. I strongly agree. There is no sense in having a separate configurable value, anyone who would think about using a PYTHONFSENCODING should just change their locale instead. Howev

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: I should not write comments so late :-p > Not after Python start. Using two encodings at the same would just ... at the same time > ... because I would like to inconsistency. because it would lead to inconsistencies --

[issue13619] Add a new codec: "locale", the current locale encoding

STINNER Victor added the comment: I would be possible to implement incremental decoder with mbsrtowcs() and incremental encoder with wcsrtombs(), by serializing mbstate_t to a long integer (TextIOWrapper.tell() does something like that). The problem is that mbsrtowcs() and wcsrtombs() are "re

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Roger Serwy added the comment: I checked the submitted patches from the issues against the large patch by eye. Guilherme's patches in these separate issues have the same contents: issue1207589, issue1612262, issue1721083, issue6699, issue3359. The large patch updates issue964437, but the "vie

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: > The main problem I see being discussed is that > changing the encoding after Python starts would > be dangerous, which I agree with, but we're not > proposing to do that. Not after Python start. Using two encodings at the same would just adds new problems. O

[issue13643] 'ascii' is a bad filesystem default encoding

Martin Pool added the comment: On 21 December 2011 11:26, STINNER Victor wrote: > I never checked which locale is used by default for programs called by cron. > So I checked: on Fedora 16, programs start with a very few environment > variables, and LANG and LC_ALL are not set. You can add "LA

[issue13643] 'ascii' is a bad filesystem default encoding

Martin Pool added the comment: On 21 December 2011 11:01, STINNER Victor wrote: > > Again: please read the discussion (in closed issues) explaing why we removed > it (and which problems it introduced). There's a lot of history, so I'm not sure exactly which problems you're referring to. The

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: > There are two problems with this: one is just the practical > one that it scales poorly to have to tell every user to do this > and to take them through working out how to set this in a way > that covers cron jobs, daemons, things run over ssh, etc. I never c

[issue13630] IDLE: Find(ed) text is not highlighted while dialog box is open

Marco Scataglini added the comment: Well I checked 'SearchBar' IDLE extension and is not bad... has some minor bugs, nothing major just very very minor quirky behavior, but nothing that seems to impair functionality AFAIK. It should be cleaned up and added to release in place of the existing

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: > If there was a separate LC_FILENAMES then Python could respect > that and insist people set it, but there isn't. During 1 month, we had PYTHONFSENCODING environment variable. It was not a good idea. Again: please read the discussion (in closed issues) explai

[issue13643] 'ascii' is a bad filesystem default encoding

Martin Pool added the comment: > I'm not sure why having a locale set to C or something invalid should be > considered a Python bug. Programs like bzr that hit these problems can tell their users, either in the docs or an error message, "change your locale to a UTF-8 one". There are two pro

[issue13616] Never ending loop in in update_refs Modules/gcmodule.c

David Butler added the comment: resolved as wont fix, because its not python's fault :) -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___

[issue13616] Never ending loop in in update_refs Modules/gcmodule.c

Amaury Forgeot d'Arc added the comment: Hey, you found it! PySide::DynamicSlotDataV2::callback() calls PyMethod_New() without getting the GIL. The Python allocator is not thread-safe, operations are supposed to be serialized by this Global Interpreter Lock. I suggest to modify this DynamicSl

[issue13616] Never ending loop in in update_refs Modules/gcmodule.c

David Butler added the comment: I think I have found the problem! I took a closer look at the Fatal error core: #0 0xb76fe424 in __kernel_vsyscall () #1 0xb740ccb1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb740e3f2 in *__GI_abort () at abort.c:92 #3 0xb76619

[issue13616] Never ending loop in in update_refs Modules/gcmodule.c

David Butler added the comment: This also looks familiar: http://bytes.com/topic/python/answers/36901-fatal-error-gc-object-already-tracked "semi-randomly locks somewhere outside my C-code (after returning to python), and semi-randomly issues a "Fatal error: GC object already tracked... " Someon

[issue13616] Never ending loop in in update_refs Modules/gcmodule.c

David Butler added the comment: I have 10 identical test machines running this this code ( operating systems are cloned ). I am not usning valgrind in these tests, it was causing various issues... (gdb) info sharedlibrary >FromTo Syms Read Shared Object Library 0xb75a02b0

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Ned Deily added the comment: Thanks, Roger. It would also be helpful if you ascertain for the overlaps which of the two versions is newer, the individual issue/path or the large feature diff. The relative import changes should not be applied in the standard library; they were specifically r

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Roger Serwy added the comment: minor mistake - issue3559 "Pasted \n not same as typed \n" -- ___ Python tracker ___ ___ Python-bugs-l

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Roger Serwy added the comment: I went through the changes in "idlelib20101012_From_r32a3.patch". A lot of the changes are for using relative imports. Those changes aside, here is a list of issues that this patch covers. Most of these issues already have patches that are included in the large

[issue13643] 'ascii' is a bad filesystem default encoding

Martin added the comment: > It was already discussed: using a different encoding for filenames and for > other things is really not a good idea. The main problem is the interaction > with other programs. Yes, for many programs, a change like this will mean they create the file, but then throw

[issue13643] 'ascii' is a bad filesystem default encoding

Martin added the comment: > I'm not sure why having a locale set to C or something invalid should be > considered a Python bug. You have to handle un-decodable filenames no > matter what you do, since things aren't always encoded in utf-8 on non-OSX > unix even when that is the system locale.

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: > under either the C locale, or with an invalid or missing locale The right fix is to fix your locale, not Python. -- ___ Python tracker ___ _

[issue13643] 'ascii' is a bad filesystem default encoding

STINNER Victor added the comment: > Currently when running Python on a non-OSX posix environment > under either the C locale, or with an invalid or missing locale, > it's not possible to operate using unicode filenames outside > the ascii range. It was already discussed: using a different encod

[issue13643] 'ascii' is a bad filesystem default encoding

R. David Murray added the comment: I'm not sure why having a locale set to C or something invalid should be considered a Python bug. You have to handle un-decodable filenames no matter what you do, since things aren't always encoded in utf-8 on non-OSX unix even when that is the system local

[issue13643] 'ascii' is a bad filesystem default encoding

New submission from Martin : Currently when running Python on a non-OSX posix environment under either the C locale, or with an invalid or missing locale, it's not possible to operate using unicode filenames outside the ascii range. Using bytes works, as does reading expecting unicode, using t

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Changes by Hynek Schlawack : Removed file: http://bugs.python.org/file24062/8a9e14cda106.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Changes by Hynek Schlawack : Added file: http://bugs.python.org/file24063/c02fbcda56f3.diff ___ Python tracker ___ ___ Python-bugs-list mailin

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Hynek Schlawack added the comment: You're right. I've updated the docs accordingly, thanks! -- ___ Python tracker ___ ___ Python-bugs

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Charles-François Natali added the comment: Looks good to me, except for another minor nit: """ the elements of the `iterable` are expected to be tuples """ AFAICT, you just require the elements of `ìterables` to be iterables, not necessarily tuples. -- ___

[issue3905] subprocess failing in GUI applications on Windows

Changes by Christian Häggström : -- nosy: +chn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Changes by Hynek Schlawack : Removed file: http://bugs.python.org/file22860/mp-starmap-w-docs.diff ___ Python tracker ___ ___ Python-bugs-list

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Changes by Hynek Schlawack : Added file: http://bugs.python.org/file24062/8a9e14cda106.diff ___ Python tracker ___ ___ Python-bugs-list mailin

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Hynek Schlawack added the comment: Thanks for the feedback Antoine! I updated the patch to latest default tip and added the requested tags to the docs. -- hgrepos: +97 ___ Python tracker

[issue13051] Infinite recursion in curses.textpad.Textbox

Tycho Andersen added the comment: Attached is a patch which contains a testcase as well. A few notes about this testcase: 1. I couldn't figure out how to get it to run correctly after all the other tests had run, so I had to run it first. This seems lame. One possible fix is to run each test

[issue6321] Reload Python modules when running programs

samwyse added the comment: [issue5847] fixed in 2.7/3.1 -- resolution: -> out of date status: open -> closed ___ Python tracker ___ _

[issue13614] `setup.py register` fails if long_description contains RST

anatoly techtonik added the comment: s/commit/comment/ sry. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13614] `setup.py register` fails if long_description contains RST

anatoly techtonik added the comment: A good analysis of the issue is made by Jason Conti at Ubuntu bug report mentioned in the first commit. -- title: `setup.py register` fails with traceback -> `setup.py register` fails if long_description contains RST __

[issue13639] UnicodeDecodeError when creating tar.gz with unicode name

Changes by Antoine Pitrou : -- nosy: +lars.gustaebel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9725] urllib.request.FancyURLopener won't connect to pages requiring username and password

Changes by Joonas Kuorilehto : -- nosy: +joneskoo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Antoine Pitrou added the comment: One nit: the patch needs "versionadded" tags for the two new functions. -- ___ Python tracker ___ _

[issue13642] urllib incorrectly quotes username and password in https basic auth

New submission from Joonas Kuorilehto : Reproduction: >>> import urllib >>> urllib.urlopen("https://example.com/";) Enter username for Test Site at example.com: user Enter password for user in Test Site at example.com: top secret Enter username for Test Site at example.com: # If the correct pass

[issue12708] multiprocessing.Pool is missing a starmap[_async]() method.

Antoine Pitrou added the comment: This looks like a reasonable request to me, and the patch looks generally ok as well. -- nosy: +neologix, pitrou stage: -> patch review versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4 ___ Pyt

[issue13637] binascii.a2b_* functions could accept unicode strings

Changes by Antoine Pitrou : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue13637] binascii.a2b_* functions could accept unicode strings

Antoine Pitrou added the comment: Committed now. -- resolution: -> fixed stage: patch review -> committed/rejected ___ Python tracker ___ __

[issue13641] decoding functions in the base64 module could accept unicode strings

New submission from Antoine Pitrou : Similarly to #13637 for the binascii module, the decoding functions in the base64 module could accept ASCII-only unicode strings. -- components: Library (Lib) keywords: easy messages: 149912 nosy: pitrou priority: normal severity: normal status: open

[issue13637] binascii.a2b_* functions could accept unicode strings

Roundup Robot added the comment: New changeset eb8d62706d5f by Antoine Pitrou in branch 'default': Issue #13637: "a2b" functions in the binascii module now accept ASCII-only unicode strings. http://hg.python.org/cpython/rev/eb8d62706d5f -- nosy: +python-dev ___

[issue11867] Make test_mailbox deterministic

Roundup Robot added the comment: New changeset c9facd251725 by Charles-François Natali in branch '2.7': Followup to issue #11867: Use socketpair(), since FreeBSD < 8 doesn't really http://hg.python.org/cpython/rev/c9facd251725 New changeset 9dee8a095faf by Charles-François Natali in branch '3.2

[issue1975] signals not always delivered to main thread, since other threads have the signal unmasked

Charles-François Natali added the comment: > 1. On FreeBSD, we must assume that every blocking system call, in > *every thread*, can be interrupted, and we need to catch EINTR. That's true for every Unix. Every blocking syscall can return EINTR, and there are may non restartable syscalls. Writ

[issue13405] Add DTrace probes

Charles-François Natali added the comment: As I said, I'm skeptical about the benefit vs maintenance burden ratio, especially since cPython doesn't target performance critical applications. I just fear that's a lot of intrusive code which will only be used by a handful of people worldwild, bu

[issue13634] Python SSL stack doesn't support Compression configuration

Antoine Pitrou added the comment: Now committed in 3.3. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue13634] Python SSL stack doesn't support Compression configuration

Roundup Robot added the comment: New changeset 20b52be99b5d by Antoine Pitrou in branch 'default': Issue #13634: Add support for querying and disabling SSL compression. http://hg.python.org/cpython/rev/20b52be99b5d -- nosy: +python-dev ___ Python tra

[issue13637] binascii.a2b_* functions could accept unicode strings

Antoine Pitrou added the comment: Here is a patch. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file24060/binasciistr.patch ___ Python tracker _