Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread R. David Murray
On Mon, 06 Dec 2010 13:02:41 -0800, Raymond Hettinger wrote: > On Dec 6, 2010, at 11:40 AM, Fred Drake wrote: > > On Mon, Dec 6, 2010 at 2:21 PM, Raymond Hettinger > > wrote: > >> We really ought to stop with the SafeFoo naming convention. > >> It is only descriptive to the person who wrote the

Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread Michael Foord
On 06/12/2010 21:02, Raymond Hettinger wrote: On Dec 6, 2010, at 11:40 AM, Fred Drake wrote: On Mon, Dec 6, 2010 at 2:21 PM, Raymond Hettinger wrote: We really ought to stop with the SafeFoo naming convention. It is only descriptive to the person who wrote the class or function, not to the u

Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread Fred Drake
On Mon, Dec 6, 2010 at 4:02 PM, Raymond Hettinger wrote: > IIRC, pprint has a safe_repr() and string.Template has safe_substitute() > and pydoc has a safe import. pprint.saferepr Ok, this one's my fault as well. Probably should just be named repr. string.Template.safe_substitute Agree o

Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread Raymond Hettinger
On Dec 6, 2010, at 11:40 AM, Fred Drake wrote: > On Mon, Dec 6, 2010 at 2:21 PM, Raymond Hettinger > wrote: >> We really ought to stop with the SafeFoo naming convention. >> It is only descriptive to the person who wrote the class or function, >> not to the user who will immediately wonder, "saf

Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread Fred Drake
On Mon, Dec 6, 2010 at 2:21 PM, Raymond Hettinger wrote: > We really ought to stop with the SafeFoo naming convention. > It is only descriptive to the person who wrote the class or function, > not to the user who will immediately wonder, "safe from what?" Safe from bad vampire movies, of course!

Re: [Python-Dev] Repo frozen for 3.2

2010-12-06 Thread Raymond Hettinger
On Dec 5, 2010, at 3:36 AM, Vinay Sajip wrote: > I've just been notified via being added to the nosy list of > > http://bugs.python.org/issue10627 > > about the deprecation of ConfigParser for 3.2. I presume I was added to this > list because logging.config uses ConfigParser, but logging.config

Re: [Python-Dev] Repo frozen for 3.2

2010-12-05 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/2010 01:06 PM, s...@pobox.com wrote: > > Vinay> ... the deprecation of ConfigParser for 3.2 > > What's the rush? It's been deprecated, not removed. Having modules in the stdlib ship trigger (not raise) DeprecationWarnings is bad ho

Re: [Python-Dev] Repo frozen for 3.2

2010-12-05 Thread skip
Vinay> ... the deprecation of ConfigParser for 3.2 What's the rush? It's been deprecated, not removed. Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.o

Re: [Python-Dev] Repo frozen for 3.2

2010-12-05 Thread Fred Drake
2010/12/5 Łukasz Langa : > On a related note, if you're sure logging users don't use any interpolation, > you can also use SafeConfigParser(interpolation=None) so then all values > become raw by default (e.g. people can use Python string formatting > directives, % signs etc.). We can discuss this l

Re: [Python-Dev] Repo frozen for 3.2

2010-12-05 Thread Łukasz Langa
Reposted for reference what originally only went to Vinay. Wiadomość napisana przez Vinay Sajip w dniu 2010-12-05, o godz. 12:36: > I've just been notified via being added to the nosy list of > > http://bugs.python.org/issue10627 > > about the deprecation of ConfigParser for 3.2. I presume I wa

[Python-Dev] Repo frozen for 3.2

2010-12-05 Thread Vinay Sajip
I've just been notified via being added to the nosy list of http://bugs.python.org/issue10627 about the deprecation of ConfigParser for 3.2. I presume I was added to this list because logging.config uses ConfigParser, but logging.config doesn't use any interpolation features so I could easily cha