[issue10951] gcc 4.6 warnings

2012-09-30 Thread Martin Pool
Martin Pool added the comment: Hi, Martin, On 20 August 2012 05:25, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > (As usual), I'm quite skeptical about this "bulk bug report"; it violates the > "one bug at a time" principle, wher

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

2011-12-23 Thread Martin Pool
Martin Pool added the comment: Terry, that's fine. Thanks to everyone who contributed to the discussion. -- ___ Python tracker <http://bugs.python.org/is

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

2011-12-21 Thread Martin Pool
Martin Pool added the comment: On 22 December 2011 13:15, STINNER Victor wrote: > You cannot pass directly "h\xe9.txt", but if you know the "correct" file > system encoding, you can encode it explicitly using str.encode("utf-8"). My recollection was

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

2011-12-21 Thread Martin Pool
Martin Pool added the comment: On 22 December 2011 12:32, STINNER Victor wrote: > > STINNER Victor added the comment: > > On 22/12/2011 02:16, Martin Pool wrote: >> The proposal is that in some cases where Python currently assumes >> filenames are ascii on Linux, it

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

2011-12-21 Thread Martin Pool
Martin Pool added the comment: On 22 December 2011 11:21, STINNER Victor wrote: > This discussion is becoming very long, I didn't remember the original > purpose. The proposal is that in some cases where Python currently assumes filenames are ascii on Linux, it ought to instead

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

2011-12-21 Thread Martin Pool
Martin Pool added the comment: On 21 December 2011 12:41, Antoine Pitrou wrote: > > 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 standardiz

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

2011-12-20 Thread Martin Pool
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())" &g

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

2011-12-20 Thread Martin Pool
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

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

2011-12-20 Thread Martin Pool
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. Yo

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

2011-12-20 Thread Martin Pool
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&#x

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

2011-12-20 Thread Martin Pool
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&

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-30 Thread Martin Pool
Martin Pool added the comment: On 31 August 2011 07:56, STINNER Victor wrote: > > STINNER Victor added the comment: > >> def handler(signal, stackframe): >>     print "OUCH" >>     stdout.flush() >>     _exit(1) > > What do you want to do

[issue7584] datetime.rfcformat() for Date and Time on the Internet

2011-08-21 Thread Martin Pool
Martin Pool added the comment: Z is well established as meaning "UTC time" <http://en.wikipedia.org/wiki/Coordinated_Universal_Time#Time_zones> so shouldn't be used for "zone not known." rfc 3393 is clear that it's equivalent to +00:00. So the questio

[issue10951] gcc 4.6 warnings

2011-08-21 Thread Martin Pool
Martin Pool added the comment: My patch above fixes all the messages so that you get a clean build with the current makefile. -Wuninitialized and 'offset outside constant string' would be worth fixing but I can't reproduce them in Python. I'm personally not so keen on f

[issue10713] re module doesn't describe string boundaries for \b

2011-08-21 Thread Martin Pool
Martin Pool added the comment: > Note, 366 above confirms it's never true for an empty string. The documentation states that \B "is just the opposite of \b" yet re.match(r'\b', '') returns None and so does \B so \B isn't the opposite of \b in al

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-21 Thread Martin Pool
Martin Pool added the comment: This patch tries to improve the documentation a bit more to address the issue that confused tebeka and to advertise faulthandler. Could someone review or apply it? -- keywords: +patch Added file: http://bugs.python.org/file22989/20110822-1525-signal

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-21 Thread Martin Pool
Changes by Martin Pool : -- title: Python hang when catching a segfault -> documentation doesn't say that you can't handle C segfaults from python ___ Python tracker <http://bugs.pyth

[issue1215] Python hang when catching a segfault

2011-08-21 Thread Martin Pool
Martin Pool added the comment: The documentation for this can now point to the faulthandler module (in Python 3). -- nosy: +poolie ___ Python tracker <http://bugs.python.org/issue1

[issue10951] gcc 4.6 warnings

2011-08-21 Thread Martin Pool
Martin Pool added the comment: This fixes every compiler warning so that Python build with -Werror on Ubuntu Oneiric alpha (gcc 4.6.1-7ubuntu1). * PyMem_Resize is a macro that mutates its first argument; the return value shouldn't be used. * Some variables in sre are (appar

[issue10951] gcc 4.6 warnings

2011-08-21 Thread Martin Pool
Martin Pool added the comment: this fixes the pickle warnings, and cleans up some (I'm pretty sure) dead code in there. the pickle tests all pass. -- keywords: +patch nosy: +poolie Added file: http://bugs.python.org/file22980/20110822-1150-python-warnings