Hi, all.
I wrote a new PEP last month.
I'm sorry that I forgot to announce it here.
The pep is here:
https://peps.python.org/pep-0686/
Discussions:
* https://discuss.python.org/t/14737 (current thread)
* https://discuss.python.org/t/14435 (previous thread)
--
Inada Naoki
Gregory P. Smith writes:
> We feel it too. We've been finding Discourse more useful from a community
> moderation and thread management point of view as well as offering markdown
> text and code rendering. Ideal for PEP discussions.
The specific mention of "community moderation" and "thread
FWIW, I find Discourse (and everything similar that I've seen), awkward,
difficult to use, poorly organized, and in every way inferior to my mail
client.
Obviously, other people differ in opinion. Quite likely the majority of
cpython developers disagree. I don't think I'm entirely alone in this
On Thu, Apr 7, 2022 at 4:31 PM Jean Abou Samra wrote:
>
> I'm only a lurker here, but find the split between this mailing list
> and various Discourse categories a little confusing from the outside.
> As far as I understand, the Discourse server was originally an experiment.
> Today, it has
On 4/7/22 07:31, Petr Viktorin wrote:
On 07. 04. 22 15:59, Victor Stinner wrote:
Would it be possible to announce new PEPs on python-dev please?
Currently, all PEPs should be announced on python-dev, but not necessarily right after they're published. They should be
announced before
Le 07/04/2022 à 15:59, Victor Stinner a écrit :
Hi,
Would it be possible to announce new PEPs on python-dev please?
I don't go often to Discourse, like once a month. I don't get any
notification by email. I expected new PEPs to be announced on
python-dev, but they are not announced here
On Thu, Apr 7, 2022 at 12:02 PM Petr Viktorin wrote:
> - This API stays with the regular public API (Include/cpython/), but to
> use it you'll need to #define Py_USING_UNSTABLE_API (name up for
> bikeshedding).
Since there is already something similar called "Py_LIMITED", I
suggest dropping
On 07. 04. 22 15:59, Victor Stinner wrote:
Hi,
Would it be possible to announce new PEPs on python-dev please?
Currently, all PEPs should be announced on python-dev, but not
necessarily right after they're published. They should be announced
before submitting them to SC, though.
I don't
Hi,
Would it be possible to announce new PEPs on python-dev please?
I don't go often to Discourse, like once a month. I don't get any
notification by email. I expected new PEPs to be announced on
python-dev, but they are not announced here anymore. Is it possible to
get Discourse notifications
On Thu, Apr 7, 2022 at 5:35 AM Inada Naoki wrote:
> I just submitted the PEP 686 to the SC.
> https://github.com/python/steering-council/issues/118
>
> In this PEP, I am proposing:
>
> a. Small improvement for UTF-8 mode in Python 3.11
> b. Make UTF-8 mode default in Python 3.13.
It's easier to
IMO adding locale.getencoding() to Python 3.11 is not controversial
and is useful even if PEP 686 is rejected. This function was discussed
for 1 year (bpo-43510, bpo-43552, bpo-43557, bpo-47000) and there is
an agreement that there is a need for this function.
> Making `open(path,
So here's my proposal:
- This API stays with the regular public API (Include/cpython/), but to
use it you'll need to #define Py_USING_UNSTABLE_API (name up for
bikeshedding).
- Since we're nearing Beta and there's no rush to break things, in 3.11
you only get a warning if you try to use it
12 matches
Mail list logo
