Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-14 Thread Nick Coghlan 
On 14 October 2016 at 06:32, Guido van Rossum  wrote:
> Confirming, +1 from me. Barry, Nick? You two are the most active
> authors of PEP 1.

I've merged the PR that Barry wrote to address Mariatta's query, so I
guess that counts as +1's from both of us :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Terry Reedy 

On 10/13/2016 5:59 PM, Barry Warsaw wrote:

On Oct 13, 2016, at 05:31 PM, Terry Reedy wrote:


The major issue is making knowledge of rst and sphinx a requirement for
submitting a PEP.  I suggest making sure that PEP 1 exemplifies the preferred
usage of rst in PEPs and then suggesting using it as model.


https://github.com/python/peps/pull/115


A related issue is plain text for posting.  Initial pre-drafts can be posted
to python-ideas before being marked up.  Other than copying the browser
display of the .html conversion (which requires a bit of cleanup after
pasting), what is the easiest way to get post-markup plain text?


I don't understand the question: isn't the whole point of reST that it's a
easily readable markup language?  Just post the reST!


OK with me if that becomes the norm.  I don't think it is now.

--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Eric Snow 
On Thu, Oct 13, 2016 at 3:59 PM, Barry Warsaw  wrote:
> I don't understand the question: isn't the whole point of reST that it's a
> easily readable markup language?  Just post the reST!

+1

-eric
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Barry Warsaw 
On Oct 13, 2016, at 05:31 PM, Terry Reedy wrote:

>The major issue is making knowledge of rst and sphinx a requirement for
>submitting a PEP.  I suggest making sure that PEP 1 exemplifies the preferred
>usage of rst in PEPs and then suggesting using it as model.

https://github.com/python/peps/pull/115

>A related issue is plain text for posting.  Initial pre-drafts can be posted
>to python-ideas before being marked up.  Other than copying the browser
>display of the .html conversion (which requires a bit of cleanup after
>pasting), what is the easiest way to get post-markup plain text?

I don't understand the question: isn't the whole point of reST that it's a
easily readable markup language?  Just post the reST!

Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Terry Reedy 

On 10/13/2016 4:38 PM, Barry Warsaw wrote:

On Oct 13, 2016, at 01:32 PM, Guido van Rossum wrote:


Confirming, +1 from me. Barry, Nick? You two are the most active
authors of PEP 1.


+1 for text/x-rst being the preferred.  We'd need some time to make it the
default, but I'm generally in favor of that happening.


The major issue is making knowledge of rst and sphinx a requirement for 
submitting a PEP.  I suggest making sure that PEP 1 exemplifies the 
preferred usage of rst in PEPs and then suggesting using it as  model.


A related issue is plain text for posting.  Initial pre-drafts can be 
posted to python-ideas before being marked up.  Other than copying the 
browser display of the .html conversion (which requires a bit of cleanup 
after pasting), what is the easiest way to get post-markup plain text?


--
Terry Jan Reedy


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Barry Warsaw 
On Oct 13, 2016, at 01:32 PM, Guido van Rossum wrote:

>Confirming, +1 from me. Barry, Nick? You two are the most active
>authors of PEP 1.

+1 for text/x-rst being the preferred.  We'd need some time to make it the
default, but I'm generally in favor of that happening.  Is anybody actively
working on issue #4?

https://github.com/python/peps/issues/4

Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Guido van Rossum 
Confirming, +1 from me. Barry, Nick? You two are the most active
authors of PEP 1.

On Thu, Oct 13, 2016 at 11:43 AM, Chris Angelico  wrote:
> On Fri, Oct 14, 2016 at 5:09 AM, Mariatta Wijaya
>  wrote:
>> PEP 1 states that plain/text is an acceptable value for a PEP's content
>> type, and it is the default value if no content type is specified.
>>
>> May I propose adding something along the line of: "new PEPs should use
>> restructured Text format", and that reST format becomes the default.
>
> +1. It's already the de facto standard, and I support promoting that to de 
> jure.
>
> ChrisA
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/guido%40python.org



-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Chris Angelico 
On Fri, Oct 14, 2016 at 5:09 AM, Mariatta Wijaya
 wrote:
> PEP 1 states that plain/text is an acceptable value for a PEP's content
> type, and it is the default value if no content type is specified.
>
> May I propose adding something along the line of: "new PEPs should use
> restructured Text format", and that reST format becomes the default.

+1. It's already the de facto standard, and I support promoting that to de jure.

ChrisA
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Update to PEP 1 re: content type

2016-10-13 Thread Mariatta Wijaya 
Hello,

PEP 1 states that plain/text is an acceptable value for a PEP's content
type, and it is the default value if no content type is specified.

May I propose adding something along the line of: "new PEPs should use
restructured Text format", and that reST format becomes the default.

Based on couple tickets in peps repo, it seems like the reST format is
preferred anyway, and there have been thoughts about converting text based
PEPs into reST format
https://github.com/python/peps/issues/4
https://github.com/python/peps/issues/2

I hope this is not too controversial.
Discussed this with Guido earlier. He is supportive, and asked me to send
email to python-dev :)

Thanks


Mariatta Wijaya
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com