[Python-Dev] PEP 557 Data Classes 5th posting

2017-12-02 Thread Eric V. Smith
I've pushed another version of PEP 557. The only difference is changing the default value of "order" to False instead of True. This matches regular classes: instances can be tested for equality, but are unordered. Discussion at https://github.com/ericvsmith/dataclasses/issues/104 It's already

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntaxhighlighting)

2017-12-02 Thread Steve Dower
I tried using code blocks while writing PEP 551 but they weren’t highlighted on the python.org rendering. Personally I think it would be great, provided a good colour scheme is available (some default schemes are... not always works of art). I’m not sure who is responsible for that side of thin

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntaxhighlighting)

2017-12-02 Thread Mariatta Wijaya
If we were to add Pygments support, it is to be done in pythondotorg project. I recalled the decision was to get PEPs rendered using Sphinx and host it at Read The Docs, so we don't have to worry about updating pythondotorg. Mariatta Wijaya ___ Python-D

Re: [Python-Dev] Third and hopefully final post: PEP 557, Data Classes

2017-12-02 Thread Nick Coghlan
On 2 December 2017 at 08:15, Eric V. Smith wrote: > See https://github.com/ericvsmith/dataclasses/issues/104 for a discussion on > making order=False the default. This matches regular classes in Python 3, > which cannot be ordered. +1 for making "order=True" be explicitly opt-in. Cheers, Nick.

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntax highlighting)

2017-12-02 Thread Wes Turner
Pending a transition of PEPs to ReadTheDocs (with HTTPS on a custom domain? and redirects?) (is there a gh issue for this task?), for the pythondotorg project is it as simple as `pip install pygments` and rebuilding each .rst with docutils with pygments installed? On Saturday, December 2, 2017, Ma

Re: [Python-Dev] What's the status of PEP 505: None-aware operators?

2017-12-02 Thread Nick Coghlan
On 2 December 2017 at 12:01, Steven D'Aprano wrote: > The PEP only mentions function?() as a rejected idea, do I don't know > why we're even talking about it. The PEP is deferred, with considerable > opposition and luke-warm support, even the PEP author has said he's not > going to push for it, an

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntax highlighting)

2017-12-02 Thread Nick Coghlan
On 3 December 2017 at 12:32, Wes Turner wrote: > Pending a transition of PEPs to ReadTheDocs (with HTTPS on a custom domain? > and redirects?) (is there a gh issue for this task?), See https://github.com/python/peps/projects/1 and https://github.com/python/core-workflow/issues/5 Cheers, Nick. -

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntax highlighting)

2017-12-02 Thread Wes Turner
Add pygments for ``.. code::`` directive PEP syntax highlighting #1206 https://github.com/python/pythondotorg/issues/1206 Syntax highlighting is an advantage for writers, editors, and readers. reStructuredText PEPs are rendered into HTML with docutils. Syntax highlighting in Docutils 0.9+ is powe

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntax highlighting)

2017-12-02 Thread Serhiy Storchaka
30.11.17 15:00, Wes Turner пише: In ReStructuredText, this gets syntax highlighted because of the code directive [1][2][3]: .. code:: python    import this    def func(*args, **kwargs):        pass This also gets syntax highlighted as python[3]: .. code:: python    import this    def fu