Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/16/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > Cool. Then I'll support your support for 0o, and only using lowercase > 0b, 0o, 0x. Maybe that'll settle the discussion about this bikeshed's > color. I'm also in favor of only using lowercase j for complex and > lowercase r for raw strings.

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/16/07, Chris Monson <[EMAIL PROTECTED]> wrote: > I didn't see anyone stepping forward to write a PEP for this. If one is > needed, I'll volunteer to do it. I'm working on it! I will probably submit it tomorrow. Regards, Pat ___ Python-3000 mailin

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

I didn't see anyone stepping forward to write a PEP for this. If one is needed, I'll volunteer to do it. - C On 3/16/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: On 3/16/07, CM <[EMAIL PROTECTED]> wrote: > I'm sorry about that. I have been lurking for a long time, for some reason > under

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/16/07, CM <[EMAIL PROTECTED]> wrote: > I'm sorry about that. I have been lurking for a long time, for some reason > under this mailing address, and was forcibly reminded about that fact when I > got a moderator message when posting from a more reasonable address. The > name's Chris Monson, a

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/16/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: Um, I like to know who's speaking. "CM", "monpublic", "C" don't mean much to me. Have we met? Do you have a real name? Dos anyone here know you? (Georg perhaps?) While in general this isn't a forum where we count votes much, *anonymous* vot

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

Um, I like to know who's speaking. "CM", "monpublic", "C" don't mean much to me. Have we met? Do you have a real name? Dos anyone here know you? (Georg perhaps?) While in general this isn't a forum where we count votes much, *anonymous* votes really don't count for much at all. --Guido On 3/16/07

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

Oops, posted from the wrong email address (sorry Georg): To switch this into a positive idea from a negative one, I am -1 on using 't' -.5 on having octal literals at all, since int('0755',8) does the job nicely when needed +1 on 'o' if we must have them in the language, since the first letter o

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote: Thomas Wouters schrieb: > > > On 3/15/07, *Raymond Hettinger* <[EMAIL PROTECTED] > > wrote: > > My worry focuses on new-timers and SyntaxErrors. The worst part of > the new user experience is encountering a Syn

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/15/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > More serious is that if we want to be consistent with > 0x and allow upper case, we get 0O, which looks quite > confusing in just about any font. OR you could ban X from hex and B from binary. I have not seen a good reason why 0X0DE and 0B10 need

[Python-3000] Fwd: Re: Octal

[Alexandre Vassalotti] >I just want to mention that the issue, about removing octal literals, >has been discussed before: >http://www.python.org/dev/summary/2006-02-01_2006-02-15/#id10 LOL. Would please calendar this so that twelve months from now we can re-propose removing octal literals ;-) I

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 3/16/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > Paul Moore wrote: > > > Rather than agonise about uppercase, which is very infrequently used, > > why not just remove the option and only allow lowercase? > > That's actually a pretty good idea. Identifiers and keywords > are already case-sensitiv

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

+1 On 3/16/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > Paul Moore wrote: > > > Rather than agonise about uppercase, which is very infrequently used, > > why not just remove the option and only allow lowercase? > > That's actually a pretty good idea. Identifiers and keywords > are already case-sens

Re: [Python-3000] Proposed changes to PEP3101 advanced string formatting -- please discuss and vote!

On 3/13/07, Josiah Carlson <[EMAIL PROTECTED]> wrote: > > "Patrick Maupin" <[EMAIL PROTECTED]> wrote: > > Feature: Alternate syntaxes for escape to markup. > > this method "{foo}" escapes to markup, but when there is whitespace > > after the leading "{", e.g. "{ foo}", the brace is not an escape

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

Paul Moore wrote: > Rather than agonise about uppercase, which is very infrequently used, > why not just remove the option and only allow lowercase? That's actually a pretty good idea. Identifiers and keywords are already case-sensitive, so it's hard to see why these shouldn't be. For consistenc

Re: [Python-3000] Proposed changes to PEP3101 advanced string formatting -- please discuss and vote!

On 3/12/07, Patrick Maupin <[EMAIL PROTECTED]> wrote: > Feature: Alternate syntaxes for escape to markup. I suggest keeping this for templates, or at most the library, because ... > using decorator-style markup, e.g. [EMAIL PROTECTED] inside the string, This is effectively a command switch.

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

Nick Coghlan wrote: > 0c755 is looking like the best candidate IMO (best looking lowercase, > least bad looking uppercase) A disadvantage of 0c is that in string formatting, 'c' means 'character', confusing things slightly. -- Greg ___ Python-3000 ma

Re: [Python-3000] Misc. thoughts & questions re: xreload

You missed that it's a work in progress. I'll come back to it at some point. On 3/16/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > This is probably one of those cases where I've missed something obvious, > but shouldn't it be sufficient for xreload() to use reload() to perform the > central step

Re: [Python-3000] Octal

I just want to mention that the issue, about removing octal literals, has been discussed before: http://www.python.org/dev/summary/2006-02-01_2006-02-15/#id10 -- Alexandre ___ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman

[Python-3000] Misc. thoughts & questions re: xreload

This is probably one of those cases where I've missed something obvious, but shouldn't it be sufficient for xreload() to use reload() to perform the central step of running the code in the cleared module dictionary? There doesn't seem to be any reason to emulate all that reload() machinery, and

Re: [Python-3000] I18N identifiers

Georg Brandl schrieb: > Stephen Hansen schrieb: >> It's already there :) > > argh -- so what are we discussing here anyway? > > ;) Georg Nothing - I just wanted to ask what the status is. I still have to write that PEP yet. Regards, Martin ___ Pyth

Re: [Python-3000] Octal

On 3/16/07, Jim Jewett <[EMAIL PROTECTED]> wrote: On 3/15/07, Patrick Maupin <[EMAIL PROTECTED]> wrote: > I have not seen any real > requests for any bases other than 2, 8, 10, or 16. What is the real need for 8? Legacy protocols and such is my use case... and the benefit is not so much "in

Re: [Python-3000] Octal

On 3/15/07, Patrick Maupin <[EMAIL PROTECTED]> wrote: > I have not seen any real > requests for any bases other than 2, 8, 10, or 16. What is the real need for 8? The only use I've seen on the list is unix file permissions. Even if that weren't obscure enough to stick in a module, I would still

Re: [Python-3000] I18N identifiers

Stephen Hansen schrieb: > It's already there :) argh -- so what are we discussing here anyway? ;) Georg ___ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman

Re: [Python-3000] I18N identifiers

It's already there :) | Python 3000 source code won't use non-ASCII Unicode characters for anything except string literals or comments. | Thread: sets in P3K? http://mail.python.org/pipermail/python-3000/2006-April/001474.html On 3/16/07, Georg Brandl <[EMAIL PROTECTED]> wrote: Oleg Broytmann

Re: [Python-3000] I18N identifiers

Martin v. Löwis schrieb: > Giovanni Bajo schrieb: >>> What is the status of I18N identifiers? Has any progress been made? >>> If not, I'd like to write a PEP, and mentor a SoC student to work on >>> that (if one shows up). >> >> Is there any agreement over this feature in the first place? > > Th

Re: [Python-3000] I18N identifiers

Oleg Broytmann schrieb: > On Fri, Mar 16, 2007 at 02:27:28PM +0100, Thomas Wouters wrote: >> My recollection is that Guido said 'no' to non-ASCII identifiers (although >> that may be wishful thinking on my part.) > >I certainly remember him saying that. Me too! ;) Perhaps we can even get him

Re: [Python-3000] I18N identifiers

On Fri, Mar 16, 2007 at 02:27:28PM +0100, Thomas Wouters wrote: > My recollection is that Guido said 'no' to non-ASCII identifiers (although > that may be wishful thinking on my part.) I certainly remember him saying that. Oleg. -- Oleg Broytmannhttp://phd.pp.ru/[

Re: [Python-3000] I18N identifiers

On 3/16/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: Giovanni Bajo schrieb: >> What is the status of I18N identifiers? Has any progress been made? >> If not, I'd like to write a PEP, and mentor a SoC student to work on >> that (if one shows up). > > Is there any agreement over this feature i

Re: [Python-3000] I18N identifiers

Giovanni Bajo schrieb: >> What is the status of I18N identifiers? Has any progress been made? >> If not, I'd like to write a PEP, and mentor a SoC student to work on >> that (if one shows up). > > Is there any agreement over this feature in the first place? This counter-question may be an answer

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

On 16/03/07, Nick Coghlan <[EMAIL PROTECTED]> wrote: > There aren't many people that write UR"WTF?" either, but odd > capitalisation is still legal syntax that can't be ignored completely > when making changes. > > Compare: > > 0t755 0T755 > 0o755 0O755 > 0c755 0C755 > > 0c755 is looking like

Re: [Python-3000] I18N identifiers

On 15/03/2007 11.29, Martin v. Löwis wrote: > What is the status of I18N identifiers? Has any progress been made? > If not, I'd like to write a PEP, and mentor a SoC student to work on > that (if one shows up). Is there any agreement over this feature in the first place? FWIW I am a strong -1 on

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

0c755 is looking like the best candidate IMO (best looking lowercase, least bad looking uppercase) So agree. :) Please? -- Stephen Hansen Development Advanced Prepress Technology [EMAIL PROTECTED] (818) 748-9282 ___ Python-3000 mailing list Python-3

Re: [Python-3000] Fwd: Re: Fwd: Re: Fwd: Re: Octal

Georg Brandl wrote: > Greg Ewing schrieb: >> More serious is that if we want to be consistent with >> 0x and allow upper case, we get 0O, which looks quite >> confusing in just about any font. > > Hm, I don't think there are too many people who write 0XABC today. > As discussed earlier, you lose t