Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-17 Thread rantingrick
On Jul 17, 6:11 am, Tim Chase wrote: > On 07/16/2011 10:10 PM, Steven D'Aprano wrote: > > > But I've never come across an email client that messes with > > attachments. Just send your code as an attached .py file and > > it's all good. > > However I'm on a couple mailing lists (e.g. lurking on Ope

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-17 Thread Tim Chase
On 07/16/2011 10:10 PM, Steven D'Aprano wrote: But I've never come across an email client that messes with attachments. Just send your code as an attached .py file and it's all good. However I'm on a couple mailing lists (e.g. lurking on OpenBSD) that strip all attachments... -tkc -- http

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Steven D'Aprano
Michael Hrivnak wrote: > Dodgy medium? Such as? I just avoid sending code over any medium > that is going to change the text in any way. Are you sending it with > an instant messenger client or something? There are lots of ways, > some very convenient, to transfer files without them being modi

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Chris Angelico
On Sun, Jul 17, 2011 at 9:25 AM, rantingrick wrote: > Now you see what this four space "brain washing" has done to us! > At least we have clean, freshly-washed brains. ChrisA -- http://mail.python.org/mailman/listinfo/python-list

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Andrew Berg
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On 2011.07.16 06:12 PM, Chris Angelico wrote: > He's on Steven's killfile, and he might get himself on mine. He's like a guy at a party who's had too much to drink. He'll start going on about conspiracy theories and philosophies based more on bloo

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread rantingrick
On Jul 16, 6:03 pm, Andrew Berg wrote: > Shouldn't that be s = s.replace('--->', '\t') ? Now you see what this four space "brain washing" has done to us! -- http://mail.python.org/mailman/listinfo/python-list

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Chris Angelico
On Sun, Jul 17, 2011 at 5:23 AM, Michael Hrivnak wrote: > Dodgy medium?  Such as?  I just avoid sending code over any medium > that is going to change the text in any way.  Are you sending it with > an instant messenger client or something?  There are lots of ways, > some very convenient, to trans

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Andrew Berg
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On 2011.07.16 10:32 AM, rantingrick wrote: > This method will preserve indention. However some might > blubber..."Yeah but then you have to remove the arrows, boo :( "... > well just watch and learn kiddo: > s = """ > def foo(): --->for x

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Michael Hrivnak
Dodgy medium? Such as? I just avoid sending code over any medium that is going to change the text in any way. Are you sending it with an instant messenger client or something? There are lots of ways, some very convenient, to transfer files without them being modified. If you need to quickly sha

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread Chris Angelico
On Sun, Jul 17, 2011 at 1:32 AM, rantingrick wrote: > On Jul 15, 6:16 pm, Chris Angelico wrote: >> Not Ruby, but to other languages. There's this guy in my house named >> Chris who tries his best to avoid Python if the code is going to be >> shared over any "dodgy medium" where indentation might

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-16 Thread rantingrick
On Jul 15, 6:16 pm, Chris Angelico wrote: > On Sat, Jul 16, 2011 at 4:56 AM, rantingrick wrote: > > Hmm, that's strange considering that code MUST be formatted in certain > > ways or you get a syntax error (indention, colons, parenthesis, etc, > > etc). I don't hear the masses claiming that they

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-15 Thread Chris Angelico
On Sat, Jul 16, 2011 at 4:56 AM, rantingrick wrote: > Hmm, that's strange considering that code MUST be formatted in certain > ways or you get a syntax error (indention, colons, parenthesis, etc, > etc). I don't hear the masses claiming that they are going over to > Ruby simply because of indentio

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-15 Thread rantingrick
On Jul 15, 2:13 am, Chris Angelico wrote: > On Fri, Jul 15, 2011 at 9:02 AM, rantingrick wrote: > > Too many folks > > are refusing to document properly and so i will take this time to > > hammer out a spec. > > The tighter you squeeze your fist, Lord Rick, the more star > programmers will slip t

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-15 Thread George Rodrigues da Cunha Silva
Em sexta-feira, 15 de julho de 2011 04:13:43, Chris Angelico escreveu: On Fri, Jul 15, 2011 at 9:02 AM, rantingrick wrote: Too many folks are refusing to document properly and so i will take this time to hammer out a spec. The tighter you squeeze your fist, Lord Rick, the more star programmer

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-15 Thread Chris Angelico
On Fri, Jul 15, 2011 at 9:02 AM, rantingrick wrote: > Too many folks > are refusing to document properly and so i will take this time to > hammer out a spec. The tighter you squeeze your fist, Lord Rick, the more star programmers will slip through your fingers. Make it so docstrings HAVE to be i

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-14 Thread Michael Hrivnak
Was tried at least once before: http://www.python.org/dev/peps/pep-0287/ Check in here with your ideas: http://www.python.org/community/sigs/current/doc-sig/ Have any other languages mandated the use of a specific documentation markup? Michael On Thu, Jul 14, 2011 at 7:02 PM, rantingrick wrote

Re: Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-14 Thread Ben Finney
rantingrick writes: > --- > New Syntax Specification For Documentation Strings > --- > > """ {DOC TAG HERE}: {MODULE_NAME|SHORT_SUMMARY_HERE}. > {NEWLINE} > {LONG_DESCRIPTION_HERE} > {NEWLINE} > Arguments: (if applicable) >

Proposal to extend PEP 257 (New Documentation String Spec)

2011-07-14 Thread rantingrick
Hello Folks, Lately i have been musing over the ideas of method tagging. Specifically i am referring to method identifiers. As most of you know i had proposed to add "syntactical markers" to the language to deal with the ambiguities that arise whist eyeball parsing sub classed methods that clobbe