Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Ethan Furman
Stephen J. Turnbull wrote: Ethan Furman writes: Where does one draw the line between feature and bug? Miracle: Works as documented.[2] [2] Python is pretty miraculous, isn't it? Yes, indeed it is! :) ~Ethan~ ___ Python-Dev mailing list Pytho

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Terry Reedy
On 1/19/2012 1:04 PM, Stephen J. Turnbull wrote: Ethan Furman writes: > Where does one draw the line between feature and bug? Bug: Doesn't work as documented. The basic idea is that the x.y docs define (mostly) the x.y language. Patches to the x.y docs fix typos, omissions, ambiguiti

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Guido van Rossum
On Thu, Jan 19, 2012 at 9:46 AM, Ethan Furman wrote: > Guido van Rossum wrote: > > We should not encourage people to write code that works with a certain > > bugfix release but not with the previous bugfix release of the same > > feature release. > > Then what's the point of a bug-fix release? I

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Michael Foord
On 19/01/2012 17:46, Ethan Furman wrote: Guido van Rossum wrote: > We should not encourage people to write code that works with a certain > bugfix release but not with the previous bugfix release of the same > feature release. Then what's the point of a bug-fix release? If 3.2.1 had broken thr

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Ethan Furman
Guido van Rossum wrote: > We should not encourage people to write code that works with a certain > bugfix release but not with the previous bugfix release of the same > feature release. Then what's the point of a bug-fix release? If 3.2.1 had broken threading, wouldn't we fix it in 3.2.2 and en

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Stephen J. Turnbull
Ethan Furman writes: > Where does one draw the line between feature and bug? Bug: Doesn't work as documented. Feature: Works as expected but not documented[1] to do so. Miracle: Works as documented.[2] Unspecified behavior that doesn't work as you expect is the unmarked case (ie, none of

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Guido van Rossum
On Thu, Jan 19, 2012 at 8:36 AM, Ethan Furman wrote: > Benjamin Peterson wrote: > >> 2012/1/19 Victor Stinner **: >> >>> http://bugs.python.org/**issue12773 :) >>> The bug is marked as close, whereas the bug exists in Python 3.2 and >>> has no been closed.

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Ethan Furman
Benjamin Peterson wrote: 2012/1/19 Victor Stinner : http://bugs.python.org/issue12773 :) The bug is marked as close, whereas the bug exists in Python 3.2 and has no been closed. The fix must be backported. It's not a bug; it's a feature. Where does one draw the line between feature and bug

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Benjamin Peterson
2012/1/19 Victor Stinner : >> http://bugs.python.org/issue12773  :) > > The bug is marked as close, whereas the bug exists in Python 3.2 and > has no been closed. The fix must be backported. It's not a bug; it's a feature. -- Regards, Benjamin ___ Py

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Antoine Pitrou
On Wed, 18 Jan 2012 20:31:38 -0700 Eric Snow wrote: > > > > Should I create a bug report? > > http://bugs.python.org/issue12773 :) Well done Eric :) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-de

Re: [Python-Dev] Writable __doc__

2012-01-19 Thread Victor Stinner
> http://bugs.python.org/issue12773  :) The bug is marked as close, whereas the bug exists in Python 3.2 and has no been closed. The fix must be backported. Victor ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo

Re: [Python-Dev] Writable __doc__

2012-01-18 Thread Noufal Ibrahim
Noufal Ibrahim writes: [...] > That is why you're seeing this. What's the question here? [...] My apologies. I didn't read the whole thread. -- ~noufal http://nibrahim.net.in Some bird populations soaring down -Headline of an article in Science News, page 126, February 20, 1993. _

Re: [Python-Dev] Writable __doc__

2012-01-18 Thread Noufal Ibrahim
Sreenivas Reddy T writes: > this is happening on python 2.6 too. > > Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) > [GCC 4.4.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. class Test(type): > ... __doc__= > File "", line 2 > __doc__= >

Re: [Python-Dev] Writable __doc__

2012-01-18 Thread Sreenivas Reddy T
this is happening on python 2.6 too. Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> class Test(type): ... __doc__= File "", line 2 __doc__= ^ SyntaxError: invalid syntax >>> cl

Re: [Python-Dev] Writable __doc__

2012-01-18 Thread Eric Snow
On Wed, Jan 18, 2012 at 5:01 PM, Ethan Furman wrote: > Is there a reason why normal classes can't have their __doc__ strings > rewritten?  Creating a do-nothing metaclass seems like overkill for such a > simple operation. > > Python 3.2 ... on win32 > --> class Test(): > ...   __doc__ = 'am I perm

Re: [Python-Dev] Writable __doc__

2012-01-18 Thread Benjamin Peterson
2012/1/18 Ethan Furman : > Is there a reason why normal classes can't have their __doc__ strings > rewritten?  Creating a do-nothing metaclass seems like overkill for such a > simple operation. > > Python 3.2 ... on win32 > --> class Test(): > ...   __doc__ = 'am I permanent?' > ... > --> Test.__do