[issue4621] zipfile returns string but expects binary

Glenn Linderman added the comment: I just "discovered" that attempting to open zip member "test\file" fails where attempting to open "test/file" works. Granted the zip contains "/" not "\" characters, but using the os.path stuff (on windows) to manipulate the names before attempting to open

[issue8243] curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR'

Changes by Daniel Vim <333...@gmail.com>: -- files: curses_bug.py nosy: theosp severity: normal status: open title: curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR' type: behavior versions: Python 2.6 Added file: http://bugs.python.org/file

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Gabriel Genellina added the comment: @jpfarias: could you be more specific? Which error(s) do you have? in which scenario? -- ___ Python tracker ___

[issue8242] Support surrogates in import ; install Python in a non-ASCII directory

STINNER Victor added the comment: > Initialize Py_FileSystemDefaultEncoding earlier in Py_InitializeEx(), > because its value is required to encode unicode using surrogates to bytes Oh, it doesn't work: get_codeset() returns NULL, because the codec register is empty when get_codeset() is calle

[issue8086] ssl.get_server_certificate new line missing

Kyle VanderBeek added the comment: Forgot to note that my patch is against 2.7 current trunk. -- nosy: +kylev ___ Python tracker ___ _

[issue8086] ssl.get_server_certificate new line missing

Changes by Kyle VanderBeek : -- keywords: +patch Added file: http://bugs.python.org/file16672/python-ssl-PEM_FOOTER.patch ___ Python tracker ___ __

[issue8242] Support surrogates in import ; install Python in a non-ASCII directory

STINNER Victor added the comment: If I understood correctly, my patch is also required to import a module having a non-ASCII full path if the file system encoding is ASCII. -- ___ Python tracker __

[issue8242] Support surrogates in import ; install Python in a non-ASCII directory

New submission from STINNER Victor : If the fullpath to the python3 binary contains a non-ASCII character and the file system encoding is ASCII, Python fails with: --- Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:]

[issue8241] py2_test_grammar.py contains invalid syntax for 2.6

Benjamin Peterson added the comment: The correct thing to do is actually to ignore py2_test_grammar.py when compiling the pyc files. -- assignee: benjamin.peterson -> loewis nosy: +loewis ___ Python tracker __

[issue8218] typo currect

Ezio Melotti added the comment: See also #8234 that has a patch with some rephrasing too. -- nosy: +ubershmekel stage: -> needs patch ___ Python tracker ___

[issue8234] Spelling and text in howto/webservers

Ezio Melotti added the comment: Closed as duplicate of #8218. -- nosy: +ezio.melotti resolution: -> duplicate stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue8241] py2_test_grammar.py contains invalid syntax for 2.6

Changes by Ezio Melotti : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson priority: -> normal stage: -> needs patch ___ Python tracker ___ __

[issue8241] py2_test_grammar.py contains invalid syntax for 2.6

New submission from Gabriel Genellina : Lib\lib2to3\tests\data\py2_test_grammar.py, in test_with_statement, requires a variant of the with statement (multiple targets) that is not available in Python 2.6. Compiling py2_test_grammar.py raises a SyntaxError. This makes the 2.6.5 installer exit

[issue4749] Issue with RotatingFileHandler logging handler on Windows

João Paulo Farias added the comment: I dont see the resolution for this problem yet... What should I do to not have it happen? -- nosy: +jpfarias ___ Python tracker ___

[issue1220212] os.kill on windows

Michael Foord added the comment: Aaaand the IronPython implementation of NativeSignal.GenerateConsoleCtrlEvent(PythonSignal.CTRL_C_EVENT, ...) delegates to Kernel32.GenerateConsoleCtrlEvent. -- ___ Python tracker

[issue6716] Windows install error when choosing to compile .py files

Gabriel Genellina added the comment: Sorry for being so terse and not filling in the gaps! In the end, I changed my mind on this bug - it's not an installer issue. The 2.6.5 MSI installer, when asked to compile .pyc files, exits with an error as reported here: http://mail.python.org/pipermail

[issue1220212] os.kill on windows

Michael Foord added the comment: I'm wrong. First IronPython tries: NativeSignal.GenerateConsoleCtrlEvent(PythonSignal.CTRL_C_EVENT, ...) But with the comment: //The following calls to GenerateConsoleCtrlEvent will fail under //most circumstances. We'll try them any ways though as this seems

[issue1220212] os.kill on windows

Changes by Michael Foord : -- versions: +Python 2.7, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue1220212] os.kill on windows

Michael Foord added the comment: It would be really useful to be able to send signal.SIGINT to processes on Windows using os.kill(...). The patch as described sounds like it would have a different signature to the standard implementation of os.kill(...) which takes a pid and a signal type.

[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0

Changes by Peter Kleiweg : -- nosy: +pebbe ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Augie Fackler : -- nosy: +durin42 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Larry Hastings : -- nosy: +larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7946] Convoy effect with I/O bound threads and New GIL

Nir Aides added the comment: > But on a busy system, won't measuring wall clock time rather than CPU time > give bogus results? This was the motivation for using clock_gettime(). I tried the wall clock version under load (including on single core system) and it seems to behave. Now it remain

[issue7946] Convoy effect with I/O bound threads and New GIL

Antoine Pitrou added the comment: > I also switched to gettimeofday() so it should work now on all Posix > with high resolution timer But on a busy system, won't measuring wall clock time rather than CPU time give bogus results? -- ___ Python trac

[issue8222] enabling SSL_MODE_AUTO_RETRY on SSL sockets

Antoine Pitrou added the comment: Fixed in r79448 (trunk), r79449 (py3k), r79451 (2.6), r79453 (3.1). -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: Switching to a documentation issue is fine to me. Indeed I can just cache the result of StringIO.getvalue(), although it feels a bit crude. I won't be able to create a documentation patch since English is not my primary language. While you're at it, the doc says about

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Antoine Pitrou added the comment: > pitrou: that's debatable, since the Python programmer has no control > over memory pointers. No, but he has control over whether he always uses the same object, or generates a new argument everytime. > As I said, I have a cStringIO buffer, and two consecuti

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: pitrou: that's debatable, since the Python programmer has no control over memory pointers. As I said, I have a cStringIO buffer, and two consecutive calls to buffer.getvalue() yield different objects. What can I do about it? I think it's a rather sane scenario, and I

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: r.david.murray: ah, sure :) However, I'm not sure a test case is absolutely required for this issue for two reasons: - the fix is trivial: it's a one-liner that enables a SSL mode that explicitely authorizes SSL_write to be called a second time with a a different me

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Antoine Pitrou added the comment: Since this error seems to be aimed at warning about potential programming errors, I'm not sure it should be silenced. The obvious fix should be to pass the same argument every time (until the data finally gets written). -- nosy: +pitrou _

[issue6716] Windows install error when choosing to compile .py files

Martin v. Löwis added the comment: Gabriel: can you explain why that should be backported? -- ___ Python tracker ___ ___ Python-bugs-l

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Changes by Antoine Pitrou : -- nosy: +janssen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue8222] enabling SSL_MODE_AUTO_RETRY on SSL sockets

Antoine Pitrou added the comment: > Would it be possible to add an option to disable SSL_MODE_AUTO_RETRY > for a specific socket? Existing applications may rely on / prefer the > current behaviour. I don't think so, since recv() used to emulate that behaviour anyway. -- __

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

R. David Murray added the comment: "test needed" is in reference to your assertion that you weren't sure your test would fail reliably. A test that fails some times and passes some times is...suboptimal when dealing with a buildbot testing infrastructure :) -- nosy: +r.david.murray

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Guilherme Salgado : -- nosy: +salgado ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: I forgot to talk about the conditions in which I stumbled upon that bug. I use a cStringIO.StringIO as a send buffer. When the socket is ready to send data, I call ssl_socket.send(send_buffer.getvalue()). Unfortunately, two consecutive calls to send_buffer.getvalue()

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: You're right about the assert, I've just uploaded a new patch. In non-blocking mode, ssl_socket.send(data) will return either 0 (which means nothing was sent, you'll have to try again), or len(data) when everything was sent. It can't return anything inbetween. This is

[issue8222] enabling SSL_MODE_AUTO_RETRY on SSL sockets

STINNER Victor added the comment: Would it be possible to add an option to disable SSL_MODE_AUTO_RETRY for a specific socket? Existing applications may rely on / prefer the current behaviour. -- ___ Python tracker

[issue8222] enabling SSL_MODE_AUTO_RETRY on SSL sockets

STINNER Victor added the comment: > letting the C OpenSSL runtime do it for us is certainly more efficient +1 if it's more efficient ;-) -- ___ Python tracker ___ __

[issue8222] enabling SSL_MODE_AUTO_RETRY on SSL sockets

STINNER Victor added the comment: See also issue #8240 about SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER (ssl.SSLSocket.write may fail on non-blocking sockets). -- nosy: +haypo ___ Python tracker _

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

STINNER Victor added the comment: If I understood correctly, the patch only concerns non blocking socket if SSL_write() returns 0? If SSL_write() returns a non zero value, can you use: ssl_socket.send(data[count:])? About the string identifier trick, you should add an assertion to ensure that

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Alexandre Conrad : -- nosy: +aconrad ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Konrad Delong : -- nosy: +konryd ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8237] multiprocessing.Queue() blocks program

Erdem U. Altinyurt added the comment: Firstly I think as you but this is not correct. Added Q.full() to know if Queue is full or not to the testQ code.. def testQ(): for i in range(1): mp.Process( None, QueueWorker, None, (i,Q,lock) ).start() while len(mp.active_children())>=

[issue6543] traceback presented in wrong encoding

STINNER Victor added the comment: > "surrogateescape" characters are not printable stderr uses backslashescape error handler, and so non-decodable characters will be displayed as \xHH. ... see also #8092 :-) -- ___ Python tracker

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Changes by R. David Murray : -- priority: -> normal stage: -> test needed type: -> behavior ___ Python tracker ___ ___ Python-bugs-l

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Changes by R. David Murray : -- components: +Extension Modules -Library (Lib) nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: The following test case exhibits the bug, but I'm not sure it will fail every time as it depends on 2 things: - your connection speed (I guess) - I used the following trick to have 2 identical strings with a different id (memory address): data = (('xx'[0] + 'xx'[1:

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

New submission from Cyril : ssl.SSLSocket.write on non-blocking sockets will fail with: _ssl.c:1217: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry on a write retry, if the buffer address has changed between the initial call and the retry (when the initial call returned 0 bytes

[issue8237] multiprocessing.Queue() blocks program

Jesse Noller added the comment: multiprocessing.Queue.Put() acts the same as Queue.put() - if the queue is full, the put call "hangs" until the queue is no longer full. The process will not exit, as the Queue is full, and it's waiting in put. This works as designed, unless I'm missing somethi

[issue8193] test_zlib fails with zlib 1.2.4

Amaury Forgeot d'Arc added the comment: According to http://www.zlib.net/ChangeLog.txt, since zlib 1.2.3.5:: - Use zlib header window size if windowBits is 0 in inflateInit2() The failing test should be changed, for example:: self.assertRaises(ValueError, zlib.decompressobj, -1) --

[issue8237] multiprocessing.Queue() blocks program

R. David Murray added the comment: Crash is for interpreter segfaults, changing to type 'behavior'. Setting stage to 'test needed' because if this is a valid bug the test will need to be turned into a unit test. -- nosy: +jnoller, r.david.murray priority: -> normal stage: -> test n

[issue8236] ./configure: ImportError: No module named asdl

R. David Murray added the comment: I can't reproduce this on 2.6 maint on Linux 32 bit (Gentoo). Did you try doing a make distclean before redoing the configure/make? -- nosy: +benjamin.peterson, r.david.murray priority: -> high ___ Python tracker

[issue8239] Windows 2.6.5 Installer Advanced Option Generates Error Message During Compile Step

Brian Curtin added the comment: This is fixed as of r79248. -- nosy: +brian.curtin priority: -> normal resolution: -> duplicate status: open -> closed ___ Python tracker ___ __

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

STINNER Victor added the comment: In Python 2.6/3.1, xmlrpclib.Transport.parse_response() accepts a file like object. But Python 2.7/3.2 requires a HTTPResponse object because parse_response() calls response.getheader() method. The patch moves the call to .getheader() in single_request() to a

[issue8239] Windows 2.6.5 Installer Advanced Option Generates Error Message During Compile Step

New submission from Peter : If the installer is run in Windows XP/SP3 without selecting the Advanced compiling option, it works fine. If the installer is run in Windows XP/SP3 and the Advanced compiling option is selected, the following error message is generated during the compile step: "Th

[issue8238] Proxy handling

Ciprian Trofin added the comment: I attached a screenshot. The proxy is on the corporate network. I'm not setting it up, I'm only using it. Internet Explorer needs that setting in order to connect. Firefox needs this proxy set as "manual proxy configuration". I looked deeper into the situati

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Dirkjan Ochtman : -- nosy: +djc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue6716] Windows install error when choosing to compile .py files

Gabriel Genellina added the comment: r78994 (exclude 2to3 tests from compileall) should be backported to trunk and the 2.6 branch, but I don't see them (yet). -- nosy: +gagenellina ___ Python tracker _

[issue8238] Proxy handling

Senthil Kumaran added the comment: How are setting up and using your proxy? It would also help you discuss your approach at python-h...@python.org and if you see any specific issues, raise it in the bug report. -- nosy: +orsenthil ___ Python tracke

[issue8238] Proxy handling

New submission from Ciprian Trofin : After I installed Python 2.6.5, I noticed a drop in performance of web connections via proxy. This script: - import time import urllib2 timeMark = time.time() opener = urllib2.build_opener() textWeb =

[issue2698] Extension module build fails for MinGW: missing vcvarsall.bat

Eric Devolder added the comment: This seems to be fixed now under 3.1.2, and works properly for me. Great stuff, thank you. Eric P.S. Last time I mistakenly tagged the bug to be "Python 3.2" as well, correcting this now. -- versions: -Python 3.2 ___