On Fri, Jan 21, 2011 at 1:46 AM, Guido van Rossum gu...@python.org wrote:
On Thu, Jan 20, 2011 at 5:16 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Thu, Jan 20, 2011 at 10:08 PM, Simon Cross
hodgestar+python...@gmail.com wrote:
I'm changing my vote on this to a +1 for two reasons:
*
On Fri, Jan 21, 2011 at 2:59 PM, Nick Coghlan ncogh...@gmail.com wrote:
These all sound like good reasons to continue to *advise* against
using non-ASCII module names. But aside from that, they sound exactly
like a lot of the arguments we heard when Py3k started enforcing the
bytes/text
Nick Coghlan writes:
On Fri, Jan 21, 2011 at 3:44 PM, Atsuo Ishimoto ishim...@gembook.org wrote:
I don't want Python to encourage people to use non-ascii module names.
I don't think anybody is *encouraging* it. The argument is for
*permitting* it, partly for consistency with other
I don't want Python to encourage people to use non-ascii module names.
I don't think the feature is open for debate anymore. PEP 3131 has been
accepted (after *long* debates), and I'll pronounce that supporting
non-ASCII module names is a direct consequence of having it accepted.
Of course,
Atsuo Ishimoto writes:
Java, a leading language of IT industry, have already support
non-ASCII class files for years. But I've never seen such files in
production in Japan, and didn't improve situation until now.
So why wouldn't Python work the same way? The rest of the world can
use
On Thu, 20 Jan 2011 22:25:17 -0500
James Y Knight f...@fuhm.net wrote:
On Jan 20, 2011, at 3:55 PM, Antoine Pitrou wrote:
On Thu, 20 Jan 2011 15:27:08 -0500
Glyph Lefkowitz gl...@twistedmatrix.com wrote:
To support the latter, could we just make sure that zipimport has a
On Thu, 20 Jan 2011 22:16:36 -0500
James Y Knight f...@fuhm.net wrote:
On Jan 20, 2011, at 9:31 PM, Ezio Melotti wrote:
Modified: peps/trunk/pep-.txt
==
--- peps/trunk/pep-.txt (original)
+++
On Jan 21, 2011, at 6:31 AM, Antoine Pitrou wrote:
On Thu, 20 Jan 2011 22:25:17 -0500
James Y Knight f...@fuhm.net wrote:
On Jan 20, 2011, at 3:55 PM, Antoine Pitrou wrote:
(by the way, it would be nice if your text/mail editor wrapped lines at
80 characters or something)
You could
On Fri, 21 Jan 2011 08:23:31 -0500
James Y Knight f...@fuhm.net wrote:
I think most mail readers are able to word-wrap raw text correctly
(even though it still makes your messages look bad amongst a thread of
nicely-formatted 80-column messages).
The real annoyance is when reading Web
On Jan 21, 2011, at 08:23 AM, James Y Knight wrote:
Well, yes, that's a pretty annoying bug in mailman, isn't it? If only anyone
around here was involved in mailman and could fix it! :) [I've attempted to
cc this to mailman-users with this message, but since I'm not subscribed I
dunno if it'll
On Fri, Jan 21, 2011 at 5:45 PM, Stephen J. Turnbull step...@xemacs.org wrote:
Nick Coghlan writes:
On Fri, Jan 21, 2011 at 3:44 PM, Atsuo Ishimoto ishim...@gembook.org
wrote:
I don't want Python to encourage people to use non-ascii module names.
I don't think anybody is *encouraging*
ACTIVITY SUMMARY (2011-01-14 - 2011-01-21)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open2527 (+29)
closed 20228 (+36)
total 22755 (+65)
Open issues
Hi,
It looks like some people fear that non-ASCII module names will cause
troubles for the interoperability: you can try my patch attached to
issue #3080 to prevent these issues and fix all bugs :-)
http://bugs.python.org/issue3080
I should maybe create a dummy Python project using non-ASCII
On Thu, Jan 20, 2011 at 16:58, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Jan 21, 2011 at 6:42 AM, brett.cannon
python-check...@python.org wrote:
brett.cannon pushed 82d3a1b694b3 to devguide:
http://hg.python.org/devguide/rev/82d3a1b694b3
changeset: 167:82d3a1b694b3
user: Brett
It's the Emacs lovers who put that stuff in all of their files, so I
ain't touching it.
On Thu, Jan 20, 2011 at 13:06, Sandro Tosi sandro.t...@gmail.com wrote:
Hi,
On Thu, Jan 20, 2011 at 20:33, brett.cannon python-check...@python.org
wrote:
+..
+ Local Variables:
+ mode:
I don't think anybody is *encouraging* it. The argument is for
*permitting* it, partly for consistency with other identifiers, and
partly because of Python's usual consenting adults standard for
permitting dangerous practices.
I'm sorry, I was not clear. I was afraid that saying learning
Given that some of the dev guide docs cover triaging and other aspects
of managing issues on the tracker, does it make sense to offer
devguide checkin access to triagers that want it?
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
17 matches
Mail list logo
