[issue10924] Adding salt and Modular Crypt Format to crypt library.

New submission from Sean Reifschneider : Over the years I've written the same code over and over to create a random salt string of 2 characters. Worse, the Modular Crypt Format is difficult to find documentation on, so creating stronger hashed passwords is difficult to get right. To that end

[issue10923] Python 2.7 hangs on Unicode+threading

Piotr Maślanka added the comment: I runned it over again with code: print 'Acquiring lock' self.loglock.acquire() print 'Attempting to convert' if type(text) == unicode: text = text.encode('utf8', errors='strict') print 'Opening '+threadspecific with open(threadspecific, 'ab') as x: x.write(tex

[issue10922] Unexpected exception when calling function_proxy.__class__.__call__(function_proxy)

Andreas Stührk added the comment: I think this is a duplicate of issue #9756: `methoddescr_call()` checks whether the given argument is acceptable as "self" argument and does so using `PyObject_IsInstance()`. As the class in the given code returns the type of the proxied object for the `__cla

[issue10923] Python 2.7 hangs on Unicode+threading

New submission from Piotr Maślanka : Python 2.7.1(x86 MSI), binary downloaded from python.org, hangs quite reliably. Code: with open(threadspecific, 'ab') as x: txt = unicode(str_or_unicode_parameter).encode('utf8') x.write(txt+'\r\n') However, it doesn't hang if I insert a print statement b

[issue10922] Unexpected exception when calling function_proxy.__class__.__call__(function_proxy)

New submission from Daniel Neuhäuser : Upon trying to create a proxy I stumbled upon this exception: Traceback (most recent call last): File "foo.py", line 11, in p.__class__.__call__(p) SystemError: PyEval_EvalCodeEx: NULL globals Investigating further led me to this code which reproduc

[issue10921] imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly

Changes by Joe Peterson : -- components: +Documentation ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue10921] imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly

Changes by Joe Peterson : -- components: -Documentation ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue10921] imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly

Changes by Joe Peterson : Removed file: http://bugs.python.org/file20419/imaplib_Internaldate2tuple.patch ___ Python tracker ___ ___ Python-bu

[issue10921] imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly

Joe Peterson added the comment: Regarding problem #4, it actually appears that returning local time is the right thing to do, since it matches the behavior of Time2Internaldate(). Returning UTC, as the doc states, would potentially break IMAP append() that can include an internaldate possibl

[issue10915] Make the PyGILState API compatible with multiple interpreters

Graham Dumpleton added the comment: Nick, I think you are making the wrong assumption that an external threads will only ever call into the same interpreter. This is not the case. In mod_wsgi and mod_python there is a pool of external threads that for distinct HTTP requests, delegated to a sp

[issue10921] imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly, and outputs localtime (not UTC)

Changes by Joe Peterson : -- title: imaplib: Internaldate2tuple crashes, does not handle negative TZ offsets, does not handle DST correctly, and outputs localtime (not UTC) -> imaplib: Internaldate2tuple() crashes, does not handle negative TZ offsets, does not handle DST correctly, an

[issue10921] imaplib: Internaldate2tuple crashes, does not handle negative TZ offsets, does not handle DST correctly, and outputs localtime (not UTC)

Changes by Joe Peterson : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10921] imaplib: Internaldate2tuple crashes, does not handle negative TZ offsets, does not handle DST correctly, and outputs localtime (not UTC)

New submission from Joe Peterson : Internaldate2tuple() is broken in several ways. The last two issues have existed in the code for some time. New issues in Python 3: 1. It crashes with "KeyError". This is because the Mon2num dictionary's keys are strings, not bytes objects (note that other

[issue10914] Python sub-interpreter test

Amaury Forgeot d'Arc added the comment: In distutils.command.config, config().try_run(body) is probably what we need. Now, I don't know how to use it... -- ___ Python tracker _

[issue10914] Python sub-interpreter test

Antoine Pitrou added the comment: > Is it possible to use distutils to compile this test, and remove it > from the Makefile? I'm not aware that distutils is able to compile applications rather than extension modules, but that would certainly be better than a rule in the Makefile, yes.

[issue10919] Environment variables are not expanded in _winreg when using REG_EXPAND_SZ.

Richard Nienaber added the comment: Further documentation on the RegEnumValue function (used by the _winreg module): http://msdn.microsoft.com/en-us/library/ms724865(v=vs.85).aspx. The documentation doesn't say whether the string is expanded or not on retrieval. Given the current behaviour p

[issue10914] Python sub-interpreter test

Benjamin Peterson added the comment: There's already precedent for test modules in Modules/ what with xxmodule.c and _testcapimodule.c. -- nosy: +benjamin.peterson ___ Python tracker _

[issue10920] cp65001, PowerShell, Python crash.

STINNER Victor added the comment: If the "crash" is the following message, this issue is a duplicate of #6058. --- PS D:\jm> c:\python31\python.exe Fatal Python error: Py_Initialize: can't initialize sys standard streams LookupError: unknown encoding: cp65001 --- It is not a crash: Python ha

[issue10914] Python sub-interpreter test

Amaury Forgeot d'Arc added the comment: +1 for this kind of tests. But I would not have their source in the "official" Modules directory. I expect that there will be several tests of this kind, each one with different modules to import, functions to run, global settings to change. IMO the C c

[issue10920] cp65001, PowerShell, Python crash.

STINNER Victor added the comment: > PS D:\jm> chcp 65001 > Page de codes active : 65001 Please don't do that: it is useless (it doesn't help to display or read more unicode characters) and it breaks Windows console: see issue #1602 (especially msg120414 and msg126303), and maybe also issue

[issue10911] cgi: add more tests

Changes by Antoine Pitrou : -- type: -> feature request versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue10920] cp65001, PowerShell, Python crash.

Antoine Pitrou added the comment: Probably a legitimate "crash" (aka deliberate abort), since Python needs an encoding for its standard input/output text streams, and the encoding suggested by the system ("cp65001") isn't supported. -- nosy: +pitrou __

[issue10920] cp65001, PowerShell, Python crash.

Changes by Antoine Pitrou : -- nosy: +haypo priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue10917] PEP 333 link to CGI specification is broken

anatoly techtonik added the comment: No surprises. Core Python community is so old that it is unlikely that people there ever experienced online gameplay. The only online game they've ever installed was probably EVE Online and if they've installed it - that was just because Stackless wiki is

[issue10917] PEP 333 link to CGI specification is broken

Benjamin Peterson added the comment: 2011/1/16 anatoly techtonik : > > anatoly techtonik added the comment: > > Nevermind. It's just another word for gr8. Well, it really grates on the eyes. -- ___ Python tracker

[issue10917] PEP 333 link to CGI specification is broken

Benjamin Peterson added the comment: Well, that really grates on the eyes. -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Pyt

[issue10917] PEP 333 link to CGI specification is broken

anatoly techtonik added the comment: Nevermind. It's just another word for gr8. -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10917] PEP 333 link to CGI specification is broken

Georg Brandl added the comment: Not sure I understand you... -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Matthew Barnett added the comment: That line crept in somehow. As it's been there since the 2010-12-24 release and you're the first one to have a problem with it (and you've already fixed it), it looks like a new upload isn't urgently needed (I don't have any other changes to make at present

[issue10917] PEP 333 link to CGI specification is broken

anatoly techtonik added the comment: w00t -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue10920] cp65001, PowerShell, Python crash.

New submission from Jean-Michel Fauth : Just relying a discussion open on comp.lang.python, http://groups.google.com/group/comp.lang.python/browse_thread/thread/771aa9081ad6584c# 1) Windows 7, open PowerShell 2) Change code page to cp65001 3) Launch Python3.1.2 or Python3.2.rc1 -> crash Key poi

[issue10919] Environment variables are not expanded in _winreg when using REG_EXPAND_SZ.

Brian Curtin added the comment: Assigning to myself. Relevant IronPython issue: http://ironpython.codeplex.com/workitem/24042 -- assignee: -> brian.curtin components: +Extension Modules, Windows -Library (Lib) nosy: +brian.curtin stage: -> needs patch type: -> behavior _

[issue10919] Environment variables are not expanded in _winreg when using REG_EXPAND_SZ.

New submission from Richard Nienaber : According to Microsoft documentation (http://msdn.microsoft.com/en-us/library/ms724884(v=vs.85).aspx) when using the REG_EXPAND_SZ value type, environment variables (e.g. %programfiles%) should be expanded to their values (e.g. 'C:\Program Files'). I've

[issue10918] **kwargs unnecessarily restricted in API

Changes by Georg Brandl : -- assignee: -> bquinlan nosy: +bquinlan versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Pytho

[issue10918] **kwargs unnecessarily restricted in API

New submission from Adrian Dries : An API such as in, e.g. futures: def submit(self, fn, *args, **kwargs): pass cannot be used thus: submit(foo, 1, 2, fn=bar) I can see two options: either mangle the named parameters: def submit(__self, __fn, *args, **kwargs): pass Or

[issue10915] Make the PyGILState API compatible with multiple interpreters

Nick Coghlan added the comment: Added Mark Hammond to the nosy list, as the original author and implementor of PEP 311 (which added the GILState APIs). Mark, since your PEP deliberately punted on multiple interpreter support, feel free to take yourself off the list again. If you spot any glar

[issue2275] urllib/httplib header capitalization

Éric Araujo added the comment: Title case is not the right thing for all headers: TE, WWW-Authenticate, etc. While we're changing this, why not implement something to return headers in the order recommended in the RFC? (Probably another feature request) -- nosy: +eric.araujo stage:

[issue10915] Make the PyGILState API compatible with multiple interpreters

Nick Coghlan added the comment: There's no point improving the multiple interpreter support if it doesn't help applications that are currently broken because of that lack of support. I believe the patch as currently proposed actually makes things *worse*. With "autoTLSkey" as a static variabl

[issue10915] Make the PyGILState API compatible with multiple interpreters

Antoine Pitrou added the comment: > The bulk of use cases is going to be simple callbacks via the same > thread that called out of Python in the first place. [...] > This is what SWIG effectively does in its generated wrappers for > callbacks. Thanks for clarifying. I agree the TLS scheme would

[issue10917] PEP 333 link to CGI specification is broken

Georg Brandl added the comment: Fixed in r88045 (also in PEP ). -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___ __