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
Just one reply seems pretty weak of a push. However, you lose nothing by
submitting it on the issue tracker: https://bugs.python.org
I don’t have a use case for this myself, but we’ll see :)
-Emanuel
From: Python-Dev [mailto:python-dev-bounces+vgr255=live...@python.org] On
Behalf Of Tim Mitchel
Hi All,
It would be nice if the @singledispatch decorator worked on instance
methods.
I have a reference implementation on pypi that does this (
https://pypi.python.org/pypi/methoddispatch).
I posted this message to python ideas a month ago (
https://mail.python.org/pipermail/python-ideas/2016-Se
On 13/10/2016 11:41, Serhiy Storchaka wrote:
On 13.10.16 00:14, Nathaniel Smith wrote:
AFAIK basically the only project that would be affected by this is
PyPy,
And MicroPython.
And Jython, except that from the start its implementation of bytearray
deferred resizing until the proportion unuse
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:/
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
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
On Mon, Oct 10, 2016, at 14:04, MRAB wrote:
> Instead of locking the object, could we keep the GIL, but have it
> normally released?
> A thread could then still call a function such as PyWeakref_GetObject()
> that returns a borrowed reference, but only if it's holding the GIL. It
> would be able
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
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
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 form
On Thu, Oct 13, 2016 at 4:43 AM Larry Hastings wrote:
>
> On 10/10/2016 10:38 PM, Chris Angelico wrote:
>
> On Tue, Oct 11, 2016 at 8:14 AM, Larry Hastings
> wrote:
>
> These hacks where we play games with the
> reference count are mostly removed in my branch.
>
> That's exactly what I would h
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 c
Hi Alexandru,
I stumbled over this question a little late by chance.
There is the possibility to use GDB, but it is most likely that you want to use
python's pdb module, instead.
Only in rare cases, when debugging the interpreter itself, you use gdb. For
debugging Python code, use pdb or som
On Wed, 12 Oct 2016 14:14:48 -0700
Nathaniel Smith wrote:
>
> The proposal is that it should be documented as being part of the
> language spec starting in 3.4 (or whatever). So applications that
> support Python 2.7 can't rely on it, sure. But if I have an
> application that requires, say, 3.5+
On 10/10/2016 10:38 PM, Chris Angelico wrote:
On Tue, Oct 11, 2016 at 8:14 AM, Larry Hastings wrote:
These hacks where we play games with the
reference count are mostly removed in my branch.
That's exactly what I would have said, because I was assuming that
refcounts would be accurate. I'm no
> AFAIK basically the only project that would be affected by this is
> PyPy, and I when I asked on #pypy they said:
>
> njs`: I think we either plan to or already support this
>
> so I'm not sure why this is controversial.
FYI, I had filed the feature request on PyPy issue tracker.
https://bitbuc
On 13.10.16 00:14, Nathaniel Smith wrote:
AFAIK basically the only project that would be affected by this is
PyPy,
And MicroPython.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
h
18 matches
Mail list logo
