[issue6247] should we include argparse

Martin v. Löwis added the comment: One important prerequisite for including it is that the author of the code contributes it for inclusion (irrespective of any license that may allow us to fork the code), and that he, or somebody else, volunteers to maintain it. IIUC, you are not the author, so

[issue6247] should we include argparse

New submission from Ritesh Raj Sarraf : Shoudl argparse be included in the Python Standard Library. I know we already have getopt and optparse but optparse doesn't support many features easily. (like options without hyphen, nargs=*) Here a little about argparse: argparse: Python command line

[issue6242] Fix reference leak in io.StringIO

Alexandre Vassalotti added the comment: Here's an updated patch. The new patch also cleans up tp_clear, tp_traverse and tp_dealloc of io.BytesIO which used weakreflist incorrectly. I also added support for test_memoryio for adding reference leak regression tests. As you'll see, the support is a

[issue6245] Add "intel" universal architecture on OSX

Martin v. Löwis added the comment: > The details of snow leopard are under NDA, but based on public > information : This is all fine, and really not surprising. My question is: Why is that causing limited usability? I would expect that Snow Leopard just ignores the PPC bits in the universal bi

[issue2947] subprocess (Replacing popen) - add a warning / hint

R. David Murray added the comment: Applied (with spacing fix) in r73313. -- resolution: -> accepted stage: patch review -> committed/rejected status: open -> closed ___ Python tracker _

[issue4309] ctypes documentation

Michael Newman added the comment: Watch out on Line 247 of r73293: "bytes objcet" should be: "bytes object" -- ___ Python tracker ___

[issue6245] Add "intel" universal architecture on OSX

Ronald Oussoren added the comment: The details of snow leopard are under NDA, but based on public information : * Snow Leopard will only support Intel-based systems * Apple's "rosetta" dynamaic translation subsystem for running PPC code on an intel system only supports 32-bit PPC code. Ther

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Vinay Sajip added the comment: The last sentence in my last comment got truncated - it's getting late here ;-) I meant to say: If you are seeing a WindowsError with an error code of 32 (this might get lost in all the other output, but it's the first error I found - the other messages look like

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Vinay Sajip added the comment: On Ubuntu, without the locks around the os.system calls, I was not getting any errors other than file-not-found errors on blah.txt - which you would expect if another thread had just deleted the file. You didn't post the errors which your test script was generating

[issue6246] Python debugger ignores exception if instructed to return from generator

Changes by Andreas Kloeckner : -- title: Python bebugger ignores exception if instructed to return from generator -> Python debugger ignores exception if instructed to return from generator ___ Python tracker _

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Vinay Sajip added the comment: Whoops, my revised test script still had some tabs. Replacing. Further information on Windows - you sometimes get error 32 (cannot rename file because owned by another process) because of anti-virus or Windows indexing software having the file open. Can you please

[issue5377] Strange behavior when performing int on a Decimal made from -sys.maxint-1

Changes by STINNER Victor : Removed file: http://bugs.python.org/file13456/force_int-3.patch ___ Python tracker ___ ___ Python-bugs-list mailin

[issue5377] Strange behavior when performing int on a Decimal made from -sys.maxint-1

STINNER Victor added the comment: > Thanks, Victor You're welcome :-) > - I'm getting a test failure in test_class fixed > - you should probably be using sys.maxint rather than sys.maxsize done > This still doesn't fix the case of int(Fraction(2L)) fixed: Fraction uses __trunc__ rather th

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Changes by Vinay Sajip : Removed file: http://bugs.python.org/file14238/revised-logthred.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: I didn't care about the os.system() call contention because that's what caused the logging problem and that blah.txt file contention should not cause logging to fail. I also had the join calls originally but took them out to simplify the code since it seemed t

[issue6246] Python bebugger ignores exception if instructed to return from generator

New submission from Andreas Kloeckner : I get this debugger session with the attached file. Note that even though a NameError occurs, no indication of that error is visible on the debugger conosle. 8< - $ python -m pdb pdb_bug.py > /

[issue4254] _cursesmodule.c callable update_lines_cols()

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

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Vinay Sajip added the comment: I did some tests on the zip files which Frans attached to this post. The reason you are getting errors is at least partly that you are not following best practices in the test scripts. Specifically, the threads are making system calls to update and delete blah.txt

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Changes by R. David Murray : -- priority: -> normal status: closed -> open type: crash -> behavior versions: -Python 2.4, Python 2.5 ___ Python tracker ___ _

[issue6244] Support for tcl 8.6

Guilherme Polo added the comment: This is a bit misleading. Python supports compiling with Tcl 8.6 and Tkinter (and _tkinter) will work (or at least should work) with it, what is not supported are tcl/tk versions below 8.3.1. I'm ok with with patching setup.py to add this "support" for everyone

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

R. David Murray added the comment: Since it controls what is considered to be whitespace, it is possible this will lead to subtle bugs, but I agree that it seems relatively benign, especially considering 3.x's unicode orientation. So, this becomes a doc bug... -- components: -Library

[issue6245] Add "intel" universal architecture on OSX

Martin v. Löwis added the comment: What do you mean by "not 100% usable"? I would hope that a four-way binary still works just fine, no? So what are the restrictions? -- nosy: +loewis ___ Python tracker ___

[issue6244] Support for tcl 8.6

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

[issue6245] Add "intel" universal architecture on OSX

New submission from Ronald Oussoren : Apple just announced that MacOSX 10.6 ("Snow Leopard") will be released in September, and will only support intel systems. This means that the --with-universal-archs option is not 100% usable if you want to build a version of Python that specifically targe

[issue6244] Support for tcl 8.6

New submission from Michael Scherer : It seems that python do not compile with tcl 8.6. Here is a patch, done by Adam Williamson, to add this version in the supported list. We are using on mandriva since 6 months without trouble, so I think this is safe to include. The patch is against version 2.

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: I just upgraded to 2.6.2 windows from python.org and it fails as well: Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 I hope Vinay can track this down in case it's a race condition that's just moving around between versio

[issue5809] "No such file or directory" with framework build under MacOS 10.4.11

Ronald Oussoren added the comment: Fixed in r73305 (trunk), r73306 (2.6) and r73307 (3.1) That is, with the above mentioned checkins configure will give a clear error message when you specify both --enable-framework and --enable- shared. -- resolution: -> fixed status: open -> close

[issue3816] __newobj__ pickle feature is not documented

Alexandre Vassalotti added the comment: Closing as the feature is documented in the section "The __newobj__ unpickling function" of PEP 307. -- assignee: georg.brandl -> resolution: -> invalid status: open -> closed ___ Python tracker

[issue6243] getkey() can segfault in combination with curses.ungetch()

Changes by Sebastian Ramacher : -- nosy: +sebastinas ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: Thanks Lowell - good information. You have many more versions of Python "laying around" than I do. ;) -- ___ Python tracker ___ ___

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

Timothy Farrell added the comment: I've attached unittest.zip. Simply unzip it to a directory and run it. I've included a Python2.x version of the unittest for the sake of clarity. The 2.x version was developed on 2.4. The 3.x version was developed on 3.0.1 and 3.1rc1 (with identical results

[issue6243] getkey() can segfault in combination with curses.ungetch()

New submission from Trundle : Snippet to reproduce: import curses scr = curses.initscr() curses.ungetch(1025) scr.getkey() This is because `keyname()` in `PyCursesWindow_GetKey()` returns NULL which is passed to `PyString_FromString()` then. The attached patch fixes the segfault. --

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: P.S. Frans - It's good to get these other data points from you. So this is reproducible from another person and on different versions of python AND on different platforms! I wasn't expecting that at all. Thanks Frans. Is there a way we can reopen this bug?

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Lowell Alleman added the comment: I tested this against a number of different python installs that I have laying around. Here are the results that I found: Releases that reproduce this bug: Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Python 2.4.2 (#67, Sep 2

[issue6218] Make io.BytesIO and io.StringIO picklable.

Alexandre Vassalotti added the comment: I split the bug fixes in the patch into two separate issues. It looks like pickling support for io.StringIO and io.BytesIO will have to wait for 3.2. -- dependencies: +Better type checking for the arguments of io.StringIO Added file: http://bugs.p

[issue6242] Fix reference leak in io.StringIO

Antoine Pitrou added the comment: It seems wrong to call PyObject_ClearWeakRefs() in stringio_clear(). Weakrefs should only be notified when the object is deallocated, not cleared. Besides, you should add a test for this, so that the leak can be spotted with regrtest -R. -- nosy: +pitro

[issue6236] os.popen causes illegal seek on AIX in Python 3.1rc

nestor added the comment: This quick and dirty fix in pydoc.py makes so it no longer aborts help. (less behaves somewhat strange for some commands but that is better than no help at all) def pipepager(text, cmd): """Page through text by feeding it to another program.""" import subproce

[issue6242] Fix reference leak in io.StringIO

New submission from Alexandre Vassalotti : io.StringIO does not clear its reference to its attributes dictionary when deleted. This causes a leak when io.StringIO has attributes. >>> def leak(): ...for _ in range(100): ... f = io.StringIO() ... f.foo = 1 ... [39348 refs] >>> leak

[issue6241] Better type checking for the arguments of io.StringIO

New submission from Alexandre Vassalotti : The included patch makes type checking of the arguments of StringIO consistent between pyio and io. >>> import io >>> io.StringIO(b"hello") Traceback (most recent call last): ... ValueError: initial_value must be str or None, not bytes >>> io.StringIO

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: >>> import sys >>> print sys.version 2.6.1 (r261:67517, Dec 4 2008, 16:51:00) [MSC v.1500 32 bit (Intel)] I have seen this behavior in older versions as well. Interesting to see it fail in linux as well. -- ___ Pyt

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

Antoine Pitrou added the comment: > In principle, they could, yes - but what specific behavior might that > be? What will change is character classification, which I consider > fairly harmless. Also, multi-byte conversion routines will change, which > is the primary reason for leaving it modifie

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

Martin v. Löwis added the comment: > It would still be better it is was unset afterwards. Third-party > extensions could have LC_CTYPE-dependent behaviour. In principle, they could, yes - but what specific behavior might that be? What will change is character classification, which I consider fa

[issue1944] Documentation for PyUnicode_AsString (et al.) missing.

Alexandre Vassalotti added the comment: The patch looks alright. I don't like the documentation for PyUnicode_FromFormatV, however. Here's my attempt to document it: .. cfunction:: PyObject* PyUnicode_FromFormatV(const char *format, va_list vargs) Equivalent to the function :cfunc:`PyUnicod

[issue6240] API to get source encoding as defined by PEP 263

Benjamin Peterson added the comment: Already done. tokenize.detect_encoding() -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker ___ __

[issue6216] Raise Unicode KEEPALIVE_SIZE_LIMIT from 9 to 32?

Terry J. Reedy added the comment: If you write a patch, you are free to include the additional change. -- ___ Python tracker ___ ___ P

[issue6240] API to get source encoding as defined by PEP 263

New submission from Sridhar Ratnakumar : It'd be nice to get the encoding used by a specific Python file. Considering that 'print' uses sys.stdout.encoding which is always set to None when the Python process is run by subprocess, knowing the source encoding is absolutely necessary in decoding the

[issue6208] path separator output ignores shell's path separator: / instead of \

R. David Murray added the comment: So is this a cosmetic issue or a functional issue? Either way, it is a feature request and I've updated the issue to reflect that. If you want to look at the code, ntpath.py is probably the relevant module. -- priority: normal -> low resolution: inva

[issue6135] subprocess seems to use local 8-bit encoding and gives no choice

Sridhar Ratnakumar added the comment: Related discussion thread: https://answers.launchpad.net/bzr/+question/63601 -- ___ Python tracker ___ _

[issue6135] subprocess seems to use local 8-bit encoding and gives no choice

Changes by Sridhar Ratnakumar : -- versions: +Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Lowell Alleman added the comment: Robert, please provide the Python version and distribution that your are using. This should do the trick: import sys print sys.version -- Added file: http://bugs.python.org/file14227/unnamed ___ Python tracker

[issue6135] subprocess seems to use local 8-bit encoding and gives no choice

Changes by Sridhar Ratnakumar : -- nosy: +srid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: P.S. The above script and failure is running on winxp sp3. Also, if you comment out the two os.system() calls, it works just fine. They seem like they should be unrelated to the logging though. You'll also see some errors about access to the blah.txt file wh

[issue4749] Issue with RotatingFileHandler logging handler on Windows

Robert Cronk added the comment: I have a small script that reproduces the problem. I couldn't reproduce it until I added some os.system() calls in the threads that were logging. Here's the output using python 2.6.1: Traceback (most recent call last): File "C:\Python26\lib\logging\handler

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

Antoine Pitrou added the comment: It would still be better it is was unset afterwards. Third-party extensions could have LC_CTYPE-dependent behaviour. -- ___ Python tracker ___ _

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

R. David Murray added the comment: Ah, I can tell you exactly why that is, then. I noticed this in pythonrun.c while grepping the source: #ifdef HAVE_SETLOCALE /* Set up the LC_CTYPE locale, so we can obtain the locale's charset without having to switch locales. *

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

Antoine Pitrou added the comment: For some reason only LC_CTYPE is affected: >>> locale.getlocale(locale.LC_CTYPE) ('fr_FR', 'UTF8') >>> locale.getlocale(locale.LC_MESSAGES) (None, None) >>> locale.getlocale(locale.LC_TIME) (None, None) >>> locale.getlocale(locale.LC_NUMERIC) (None, None) >>> l

[issue6208] path separator output ignores shell's path separator: / instead of \

ThurnerRupert added the comment: to give an example case, running mercurial, which we do for a couple of years now with success. one install, starting it either from cmd, or mingw/msys bash: $ hg status M src\com\file.txt $ hg co -m "different path now" src/com/file.txt apart from the backsla

[issue6239] c_char_p return value returns string, not bytes

New submission from Georg Brandl : If you assign a function a restype of c_char_p, you get back a Unicode string, but you should get a bytes object. >>> from ctypes import * >>> strchr = cdll['libc.so.6'].strchr >>> strchr.restype = c_char_p >>> strchr.argtypes = [c_char_p, c_char] >>> strchr(b'

[issue6238] string.ljust documentation is missing optional fillchar description

Georg Brandl added the comment: Fixed in r73296. You shouldn't have been looking at those anyway :) -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

R. David Murray added the comment: This is definately a bug in 3.1, for the same reason that a C program uses the C locale until an explicit setlocale is done: otherwise, a non-locale-aware program can run into bugs resulting from locale issues when run under a different locale than that of the

[issue6238] string.ljust documentation is missing optional fillchar description

New submission from Jason R. Coombs : The documentation for string.ljust, string.rjust, and string.center is missing the optional parameter fillchar. The str.ljust documentation appears to be correct. This was observed in Python 2.6.2 documentation as found on the docs.python.org site at the ti

[issue6208] path separator output ignores shell's path separator: / instead of \

R. David Murray added the comment: That would mean that python's notion of which OS it was running on (windows or cygwin) would have to change depending on which shell it was lanched from. This affects far more than the path seperator, and as far as I know is not practical with the current pytho

[issue798058] IDLE / PyOS_InputHook

Changes by Guilherme Polo : -- resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue798058] IDLE / PyOS_InputHook

Guilherme Polo added the comment: Uh oh, awesome. Thanks ;) -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue798058] IDLE / PyOS_InputHook

Amaury Forgeot d'Arc added the comment: Guilherme, you did not actually close the issue -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue6194] fcntl footnote about O_SHLOCK and O_EXLOCK is misleading

Georg Brandl added the comment: Thanks, fixed in r73294. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue6099] HTTP/1.1 with keep-alive support for xmlrpclib.ServerProxy

Kristján Valur Jónsson added the comment: It turns out we need to deal with exceptions and clear the cached HTTPConnection if they happen. Also, we just deal with a ECONNRESET which can happen if there is a long delay between requests, and retry the request once in that case. New patch uploa

[issue6203] 3.x locale does not default to C, contrary to the documentation and to 2.x behavior

Georg Brandl added the comment: Deferring to Martin which one is correct :) -- assignee: georg.brandl -> loewis nosy: +loewis ___ Python tracker ___ _

[issue4309] ctypes documentation

Georg Brandl added the comment: I fixed this, and a few other bytes/string issues, in r73293. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6213] Incremental encoder incompatibility between 2.x and py3k

Walter Dörwald added the comment: AFAICR the difference is: 2.x may return any object in getstate(), but py3k must return a (buffered input, integer) tuple. Simply moving py3ks getstate/setstate implementation over to 2.x might do the trick. -- ___ P

[issue6213] Incremental encoder incompatibility between 2.x and py3k

Antoine Pitrou added the comment: Yes, I agree with py3k's behaviour. But it should be backported to 2.x as well. I don't know where the changes must be done so if someone else could do it it would be nice :-) (I'm backporting the py3k IO lib and I had to disable two tests because of this)

[issue6213] Incremental encoder incompatibility between 2.x and py3k

Walter Dörwald added the comment: This was done because the codec state is part of the return value of tell(). To have a reasonable return value (i.e. one with just the position itself) in as many cases as possible it makes sense to design the codec state in such a way, that the most common stat

[issue4829] confusing error for file("foo", "w++")

John Szakmeister added the comment: The offending lines in io.py are: modes = set(mode) if modes - set("arwb+tU") or len(mode) > len(modes): raise ValueError("invalid mode: %r" % mode) In particular, the "or len(mode) > len(modes)" is picking off the fact that there is repeated

[issue6208] path separator output ignores shell's path separator: / instead of \

ThurnerRupert added the comment: if one installes python for windows with the provided installer, and then run this python from mingw/msys or cygwin, python prints backslash as path separator instead of forward slash. it would be nice if python would notice that it was started out of bash an

[issue6216] Raise Unicode KEEPALIVE_SIZE_LIMIT from 9 to 32?

Marc-Andre Lemburg added the comment: I think we should also consider raising the free list limit of currently 1024 objects. The keep-alive optimization currently uses at most 1024 * 9 * 2 = 18432 bytes (+ pymalloc overhead) on a UCS2 build of Python in the worst case. With a limit of 32 you g

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Terry J. Reedy wrote: > In the interest of possibly improving the imminent 3.1 release, > I opened #6216 > Raise Unicode KEEPALIVE_SIZE_LIMIT from 9 to 32? Thanks for opening that ticket. > I wonder if it is possible to make it generically easier to subcla

[issue2947] subprocess (Replacing popen) - add a warning / hint

Georg Brandl added the comment: Patch looks good, except for strange code indentation in the replaced example. -- assignee: georg.brandl -> r.david.murray ___ Python tracker ___

[issue6235] \d missing from effects of re.ASCII flag

Georg Brandl added the comment: Thanks, fixed in r73285. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py