gt;
> Hosting at docs.python.org is desirable too, but it can be discussed
> later.
>
> Regards,
>
> On Sun, Feb 26, 2017 at 4:08 AM, Ned Deily wrote:
> > On Feb 25, 2017, at 13:19, Brett Cannon wrote:
> >> It's getting a little hard to tease out what exactly i
This mailing list is for the development **of** Python, not **with** it.
For build failures like this it's best to ask on python-list (and if you
search for the missing libintl_* symbols you will find they come from
gettext).
On Wed, 1 Mar 2017 at 08:10 Porel, Subrata wrote:
> Hi Team,
>
>
>
> W
I don't think a common practice has bubbled up yet for when there's both
synchronous and asynchronous versions of an API (closest I have seen is
appending an "a" to the async version but that just looks like a spelling
mistake to me most of the time). This is why the question of whether
separate mo
These questions are best asked on the core-mentorship mailing list,
Jaysinh, but to quickly answer your question:
1. Yes, tests would be appreciated.
2. Nothing from me
On Mon, 13 Mar 2017 at 08:20 Jaysinh Shukla wrote:
> Respected Members,
>
> I identified the standard module 'tabnanny' i
On Mon, 20 Mar 2017 at 04:28 Serhiy Storchaka wrote:
> What is the preferable way of getting the size of tuple, list, bytes,
> bytearray: Py_SIZE or PyTuple_GET_SIZE, PyList_GET_SIZE,
> PyBytes_GET_SIZE, PyByteArray_GET_SIZE? Are macros for concrete types
> more preferable or they are outdated?
>
I'm overall very supportive of seeing something like this make it into
Python to further strengthen duck typing in the language. I know I've
wanted something something like this since ABCs were introduced.
I personally only have one issue/clarification for the PEP.
On Mon, 20 Mar 2017 at 05:02 Iv
On Tue, 21 Mar 2017 at 09:17 Matthias Kramm via Python-Dev <
python-dev@python.org> wrote:
> On Mon, Mar 20, 2017 at 2:42 PM, Ivan Levkivskyi
> wrote:
>
> 1. Backward compatibility: People are already using ABCs, including
> generic ABCs from typing module.
> If we prohibit explicit subclassing o
On Sat, 25 Mar 2017 at 03:05 Victor Stinner
wrote:
>
> https://blog.jetbrains.com/pycharm/2017/03/inside-the-debugger-interview-with-elizaveta-shashkova/
>
> "What changed in Python 3.6 to allow this?
>
> The new frame evaluation API was introduced to CPython in PEP 523 and it
> allows to specify
On Sat, 25 Mar 2017 at 05:58 Serhiy Storchaka wrote:
> On 25.03.17 12:04, Victor Stinner wrote:
> >
> https://blog.jetbrains.com/pycharm/2017/03/inside-the-debugger-interview-with-elizaveta-shashkova/
> >
> > "What changed in Python 3.6 to allow this?
> >
> > The new frame evaluation API was intr
On Mon, 27 Mar 2017 at 03:23 Serhiy Storchaka wrote:
> A number of public typedef names without the "Py" prefix survived the
> Grand Renaming [1]. A couple of new names without the "Py" prefix were
> added after the Grand Renaming (e.g. getter and setter [2]).
>
> That names were included in the
On the two-month anniversary of the GitHub migration I'm going to delete
the old git mirror: https://github.com/python/cpython-mirror. If you have a
old PR that got closed with comments or something, now is the time to get
those comments off.
___
Python-D
On Tue, 28 Mar 2017 at 23:36 INADA Naoki wrote:
> On Tue, Mar 28, 2017 at 11:07 PM, Ned Deily wrote:
> > On Mar 28, 2017, at 08:49, INADA Naoki wrote:
> >> Currently, changelog of Python 3.7a1 [1] contains changes between
> >> 3.6b1 and 3.7a1.
> >> So lot's of bugfixes are listed twice or more
Sounds good overall! I only have one thing to suggest in regards to the
license, two grammar tweaks, and a question.
On Wed, 29 Mar 2017 at 08:10 Julien Palard via Python-Dev <
python-dev@python.org> wrote:
> [SNIP]
> Sources of translated documentation will be hosted in the Python
> organization
On Wed, 29 Mar 2017 at 13:13 Julien Palard wrote:
> Hi Brett, thanks for the feedback!
>
>
>
>
>
>
>
>
>
> Please check with the PSF that this is what we really want.
>
>
> Gladly, but … how? I'm very new to all those process and have now idea on
> how I can get in touch with PSF lawyers.
>
> Wha
On Tue, 4 Apr 2017 at 04:58 Julien Palard wrote:
> Hi, little follow-up about this PEP.
>
>
> Please check with the PSF that this is what we really want. In the past
> the suggestion has been to **not** use the PSF license with all of its
> historical baggage but instead use something like Apache
new CPython Git repository.
>
> Victor
>
> 2017-03-27 22:13 GMT+02:00 Brett Cannon :
> > On the two-month anniversary of the GitHub migration I'm going to delete
> the
> > old git mirror: https://github.com/python/cpython-mirror. If you have a
> old
> > PR th
On Mon, 10 Apr 2017 at 14:32 Steve Dower wrote:
> On 10Apr2017 1032, Ethan Furman wrote:
> > Apparently the Windows installer mentions asking for help on Python List.
>
> Yay! People actually read some of that text in the installer :)
>
> Currently the installer has the following message after yo
I don't think there's any API. Your best bet will probably be to analyze
the GitHub data.
On Tue, 18 Apr 2017 at 09:09 Louie Lu wrote:
> Hi all,
>
> After reading some topic at python-committers mailing list, some of the
> topics are around not enough reviewers to review patches, cause the devel
Thanks for this, Louie! Definitely interesting to look at what modules have
the most open patches against them (spoiler alert: it's apparently argparse
with 51).
On Tue, 25 Apr 2017 at 22:18 Louie Lu wrote:
> Hi all,
>
> Fix some pr counting issue, and now the bpo-mergerate can choose hg (the
>
On Mon, 1 May 2017 at 21:19 Nick Coghlan wrote:
> On 2 May 2017 at 07:52, Chris Angelico wrote:
> > On Tue, May 2, 2017 at 6:52 AM, Terry Reedy wrote:
> >> The promise makes it clear that breaking the property is a bug to be
> fixed.
> >> It only decreases the probability for someone who has re
On Wed, 3 May 2017 at 01:24 Victor Stinner wrote:
> Hi,
>
> I spent last week working on fixing buildbots:
>
>https://www.python.org/dev/buildbot/
>
> It should now be able again to rely on them to detect regressions.
Thanks, Victor!
> Changes:
>
> * Fix various bugs (I don't even recall
My allergies have hit me hard so I'm not thinking at full capacity, but did
we ever decide if supporting os.PathLike in the stdlib was viewed as an
enhancement or bugfix? Specifically I'm thinking of
https://bugs.python.org/issue30218 for adding support to
shutil.unpack_archive() and whether it sho
Thanks for the feedback, everyone. I'll just consider it an enhancement
then.
On Wed, 3 May 2017 at 15:07 Terry Reedy wrote:
> On 5/3/2017 2:15 PM, Brett Cannon wrote:
> > My allergies have hit me hard so I'm not thinking at full capacity, but
> > did we ever decide if
I see no issue backporting since I don't think we have any compatibility
promises when it comes to Makefile commands. Plus if the perf changes to
add PGO support could be backported then I don't see why this shouldn't be
allowed.
On Thu, 4 May 2017 at 10:15 Victor Stinner wrote:
> Hi,
>
> tl;dr
On Fri, 5 May 2017 at 09:50 Victor Stinner wrote:
> 2017-05-05 18:36 GMT+02:00 Jonathan Goble :
> > It appears to me to be an individual user rather than an organization.
>
> Oh nice, glad to meet you :-) So what do you think? Are you ok to
> remove this old clone? Or do you have reasons to keep
On Tue, 9 May 2017 at 10:59 Mark Lawrence via Python-Dev <
python-dev@python.org> wrote:
> On 09/05/2017 18:05, Ethan Furman wrote:
> > A comment on a recent SO answer [1] wondered why my aenum library wasn't
> > mentioned in the docs to help guide people that needed/wanted more
> > advanced Enum
On Tue, 9 May 2017 at 11:11 Carl Meyer wrote:
> On 05/09/2017 10:28 AM, Guido van Rossum wrote:
> > There's a proposal to change one detail of PEP 484. It currently says:
> >
> > An optional type is also automatically assumed when the default
> value is
> > |None|, for example::
> >
> >
The idea seems reasonable to me when viewing type hints as a form of
documentation as it helps remind people how they are expected to call the
final function.
One worry I do have, though, is Callable doesn't support keyword-only
parameters, so declared_type won't work in all cases without Callable
On Tue, 16 May 2017 at 08:08 Martin Wimpress
wrote:
> Hi all,
>
> I work at Canonical as part of the engineering team developing Ubuntu
> and Snapcraft [1] and I'm a long time Python fan :-)
>
> We've created snaps, a platform that enables projects to directly
> control delivery of software updat
On Fri, 26 May 2017 at 21:28 Nick Coghlan wrote:
> Hi folks,
>
> Over on
> https://github.com/pypa/python-packaging-user-guide/pull/305#issuecomment-304169735
> we're looking to update the theming of packaging.python.org to match
> that of the language documentation at docs.python.org.
>
> Doing
On Wed, 31 May 2017 at 04:01 Serhiy Storchaka wrote:
> Currently when you add a new token you need to change a couple of files:
>
> * Include/token.h
> * _PyParser_TokenNames in Parser/tokenizer.c
> * PyToken_OneChar(), PyToken_TwoChars() or PyToken_ThreeChars() in
> Parser/tokenizer.c
> * Lib/to
If you create an issue at github.com/python/peps and assign it to me I will
get to it someday. :)
On Thu, 1 Jun 2017 at 00:19 Victor Stinner wrote:
> 2017-05-31 19:27 GMT+02:00 Guido van Rossum :
> > I interpret the PEP (...)
>
> Right, the phrasing requires to "interpret" it :-)
>
> > (...) as
On Mon, 12 Jun 2017 at 01:08 Nick Coghlan wrote:
> On 12 June 2017 at 17:31, Martin (gzlist) via Python-Dev
> wrote:
> > On 12/06/2017, Serhiy Storchaka wrote:
> >>
> >> But if an error is raised when execute undo_something(), it replaces the
> >> original exception which become chaining as the
Great idea! I had thought about doing something similar to this years ago
to help diagnose when a test passes in isolation but somehow fails due to
one of the bazillion of other tests that ran previously (which can be hard
to narrow down if the failure is not early on in a test run).
On Fri, 16 Ju
While the redirect for https://docs.python.org/devguide does not exist yet,
the infrastructure team has been nice enough to set up
https://devguide.python.org for us so that the devguide is served from Read
the Docs. This not only will (eventually) let the infrastructure team have
one less custom p
FYI we're aware of the internal link problem and I've notified the
infrastructure team about it (looks like some URL rewrite rule is
misconfigured 😞).
On Wed, Jun 21, 2017, 18:14 Brett Cannon, wrote:
> While the redirect for https://docs.python.org/devguide does not exi
On Thu, 22 Jun 2017 at 02:32 Larry Hastings wrote:
>
>
> On 06/22/2017 01:04 AM, Victor Stinner wrote:
>
> About the cipher list in ssl, the change itself is simple but it's to
> blacklist DES and 3DES since it has been proved that these ciphers are
> really too weak nowadays:
>
> http://python-s
On Thu, 22 Jun 2017 at 16:26 Bhavishya wrote:
> Also I saw your conversation with "Brett Cannon" on lazy-loading some
> modules at startup, and also doing so using ModuleProxy(also several
> implementations that exist like importlib's Lazyloader
> <htt
On Sat, 24 Jun 2017 at 09:46 Larry Hastings wrote:
> On 06/24/2017 09:40 AM, Terry Reedy wrote:
>
> On 6/23/2017 11:24 PM, Larry Hastings wrote:
>
> > You can install blurb from pip:
> >
> > % pip3.6 install blurb
>
> This does not seem to work right. On Windows:
>
> C:\Users\Terry>py -3 -m
I just pushed blurb 1.0.0.post1 which re-packages everything using flit so
there's a blurb.py and an entry point for the `blurb` command. That should
meet everyone's needs for launching the tool.
On Sat, 24 Jun 2017 at 09:54 Brett Cannon wrote:
> On Sat, 24 Jun 2017 at 09:46 L
On Sat, 24 Jun 2017 at 10:07 Antoine Pitrou wrote:
>
> Larry,
>
> I have just used blurb on https://github.com/python/cpython/pull/2010
> and it was absolutely painless. Thank you!
>
> One minor thing: `make patchcheck` doesn't know to examine the NEWS.d
> directory when checking for NEWS entrie
On Sat, Jun 24, 2017, 23:45 Nick Coghlan, wrote:
> On 25 June 2017 at 16:31, Terry Reedy wrote:
> >> 25.06.17 06:04, Nick Coghlan пише:
> >>> All the PRs share an issue number in that case, so Bedevere should be
> >>> able to pick up that there's a pre-existing NEWS entry (even if it
> >>> isn't
On Sun, Jun 25, 2017, 11:24 Terry Reedy, wrote:
> On 6/25/2017 12:39 PM, Brett Cannon wrote:
>
> > The entire reason I want to have this check is I don't want or have to
> > ask another PR submitter to include a draft of a news item. It's much
> > easier to e
On Sun, 25 Jun 2017 at 20:56 Nick Coghlan wrote:
> On 26 June 2017 at 02:39, Brett Cannon wrote:
> > On Sat, Jun 24, 2017, 23:45 Nick Coghlan, wrote:
> >> I was mainly referring to cases where either an initial commit (with a
> >> complete NEWS entry) requires fo
On Mon, 26 Jun 2017 at 09:38 Victor Stinner
wrote:
> Hi,
>
> I updated my bisect_test.py script to simplify its command line:
>
>https://github.com/haypo/misc/blob/master/python/bisect_test.py
>
> To debug a reference leak in test_os, now just type:
>
>$ ./python bisect_test.py -R 3:3 tes
On Mon, 26 Jun 2017 at 14:28 Terry Reedy wrote:
> On 6/25/2017 4:09 PM, Guido van Rossum wrote:
> > On Sun, Jun 25, 2017 at 12:23 PM, Brett Cannon > <mailto:br...@python.org>> wrote:
> >
> >
> >
> > On Sun, Jun 25, 2017, 11:24 Terry R
[It seems to me most of this thread has gone off-topic since it now
includes what I consider a sexist comment, complaining about git, and
discussing people's credentials in terms of being able to comment on
something, I'm basically ignoring everything that came after this email as
none of that has
On Mon, 26 Jun 2017 at 13:38 Victor Stinner
wrote:
> 2017-06-26 21:58 GMT+02:00 Brett Cannon :
> > I don't see why regrtest isn't the right place for this.
>
> The current regrest CLI isn't designed for subcommands, and I don't
> want to "pollute
In general the answer to helping with code coverage is "whatever module
motivates you to help". :) So unless a core dev has a specific module that
they want to help you write tests for then it's whatever you want to work
on.
And for easy reference, the code coverage report can be found at
https://
A quick thanks from me, Ned, for stepping forward to help 3.3 pine for the
fjords.
On Sat, Jul 15, 2017, 14:51 Ned Deily, wrote:
> Python 3.3 is fast approaching its end-of-life date, 2017-09-29. Per our
> release policy, that date is five years after the initial release of 3.3,
> 3.3.0 final o
On Mon, 17 Jul 2017 at 13:28 Raymond Hettinger
wrote:
>
> > On Jul 17, 2017, at 8:49 AM, Guido van Rossum wrote:
> >
> > One of the reasons to be wary of exec()/eval() other than the usual
> security concerns is that in some Python implementations they have a high
> overhead to initialize the pa
On Mon, 17 Jul 2017 at 19:26 Nathaniel Smith wrote:
> On Jul 17, 2017 5:28 PM, "Steven D'Aprano" wrote:
>
> On Mon, Jul 17, 2017 at 09:31:20PM +, Brett Cannon wrote:
>
> > As for removing exec() as a goal, I'll back up Christian's point and the
>
On Tue, 18 Jul 2017 at 09:07 Ethan Furman wrote:
> Raymond Hettinger:
> -
> > One minor grumble: I think we need to give careful cost/benefit
> considerations to
> > optimizations that complicate the implementation. Over the last
> several years, the
> > source for Python has
On Thu, 20 Jul 2017 at 22:11 Chris Jerdonek
wrote:
> On Thu, Jul 20, 2017 at 8:49 PM, Nick Coghlan wrote:
> > ...
> > * Lazy loading can have a significant impact on startup time, as it
> > means you don't have to pay for the cost of finding and loading
> > modules that you don't actually end up
Thanks to Kushal Das we now have one of the most requested features since
the transition: a link in PRs back to bugs.python.org (in a more
discoverable way since we have had them since Bedevere launched :) . When a
pull request comes in with an issue number in the title (or one gets
added), a link
On Sat, Jul 22, 2017, 07:22 Steve Dower, wrote:
> I believe the trend is due to language like Python and Node.js, most of
> which aggressively discourage threading (more from the broader community
> than the core languages, but I see a lot of apps using these now), and also
> the higher reliabili
On Sun, Jul 23, 2017, 00:53 Michel Desmoulin,
wrote:
>
>
> > Optimizing startup time is incredibly valuable,
>
> I've been reading that from the beginning of this thread but I've been
> using python since the 2.4 and I never felt the burden of the startup time.
>
> I'm guessing a lot of people ar
On Sun, Jul 23, 2017, 10:52 Michel Desmoulin,
wrote:
>
>
> Le 23/07/2017 à 19:36, Brett Cannon a écrit :
> >
> >
> > On Sun, Jul 23, 2017, 00:53 Michel Desmoulin, > <mailto:desmoulinmic...@gmail.com>> wrote:
> >
> >
> >
> > >
n't find
> those quickly (PEP 512, Google search, etc) -- can someone point me in the
> right direction? -Ben
>
Basically there was push-back on the idea and I only had enough time and
patience for one major infrastructure change that was somewhat
controversial and not for two.
-Brett
I just pushed a change to Bedevere to help track what stage a pull request
is in. The stages are:
- awaiting review
- awaiting core review
- awaiting changes
- awaiting change review
- awaiting merge
The "review" stage is for when a pull request has no reviews either
approving or
Since everyone is a volunteer, Cathy, there are unfortunately no real
timelines. It really comes down to someone who feels they have the
knowledge necessary to review the PR having the spare time to do so. So
emailing here and saying, "my PR has addressed all the comments and has
been ready to go f
On Fri, 18 Aug 2017 at 02:05 Christian Tismer wrote:
> Hi friends,
>
> in the last months, I have developed signature support for
> PySide. The module creates the same signatures as are known
> for plain Python functions.
>
> As a non-trivial addition, the module also handles multiple
> signature
On Sat, Aug 19, 2017, 01:43 Antoine Pitrou wrote:
> On Fri, 18 Aug 2017 16:33:27 -0400
> Yury Selivanov wrote:
> >
> > There are a few open questions left, namely the terminology
> > and design of ContextKey API. On the former topic, I'm quite
> > happy with the latest version: Execution Contex
Thanks for all of this, Victor!
On Fri, Aug 18, 2017, 09:38 Victor Stinner wrote:
> Hi,
>
> Here is a quick report of what changed recently on buildbots.
>
>
> == pythoninfo ==
>
> I added a new "python3 -m test.pythoninfo" command which is now run on
> Travis CI, AppVeyor and buildbots.
>
>
On Sun, Aug 20, 2017, 03:08 Antoine Pitrou wrote:
> On Sat, 19 Aug 2017 17:21:03 -0700
> Guido van Rossum wrote:
> > The way we came to "logical context" was via "logical thread (of
> control)",
> > which is distinct from OS thread. But I think we might need to search for
> > another term...
>
>
On Wed, 30 Aug 2017 at 02:56 Paul Moore wrote:
> On 30 August 2017 at 10:48, Nick Coghlan wrote:
> > On 30 August 2017 at 19:39, Antoine Pitrou wrote:
> >> On Wed, 30 Aug 2017 08:48:56 +0300
> >> Serhiy Storchaka wrote:
> >>> Please, please don't forget to edit commit messages before merging.
FYI I opened https://github.com/python/cpython/pull/29170 to loosen/correct the
definition of "iterator", but I got push-back on the PR and this thread never
reached a clear conclusion. As such I'll ask the SC to make a call.
___
Python-Dev mailing list
Rendered versions can be found at the following links:
https://www.python.org/dev/peps/pep-0663/
https://python.github.io/peps/pep-0663/
On Tue, Nov 2, 2021 at 8:41 PM Ethan Furman wrote:
> See the latest changes, which are mostly a (hopefully) improved abstract,
> better tables, and some sligh
What notification? (I fully admit I may not have gotten one due to some
team I'm in, but I have no such notification if it happened recently.)
On Thu, Nov 4, 2021 at 12:16 AM Larry Hastings wrote:
>
> I guess this is part of the migration from bpo to GitHub issues? Maybe
> the initial work coul
On Tue, Nov 9, 2021 at 6:31 AM Steven D'Aprano wrote:
> By the way, this discussion is probably better suited to the
> Python-Ideas mailing list. But since we're here...
>
> On Tue, Nov 09, 2021 at 11:37:40AM +0100, Sebastian Rittau wrote:
>
> > >>To me, the "natural" solution looks like this:
>
On Sun, Nov 14, 2021 at 3:01 PM Victor Stinner wrote:
> On Sun, Nov 14, 2021 at 6:34 PM Eric V. Smith wrote:
> > On second thought, I guess the existing policy already does this. Maybe
> > we should make it more than 2 versions for deprecations? I've written
> > libraries where I support 4 or 5
On Fri, Nov 12, 2021 at 4:16 AM Victor Stinner wrote:
> > > It was decided to start deprecating the asyncore, asynchat and smtpd
> > > modules in Python 3.6 released in 2016, 5 years ago. Python 3.10 emits
> > > DeprecationWarning.
> >
> > Wait, only Python 3.10?
> > According to the policy, the
On Tue, Nov 16, 2021 at 3:05 AM Petr Viktorin wrote:
> On 12. 11. 21 13:09, Victor Stinner wrote:
> >>> It was decided to start deprecating the asyncore, asynchat and smtpd
> >>> modules in Python 3.6 released in 2016, 5 years ago. Python 3.10 emits
> >>> DeprecationWarning.
> >>
> >> Wait, only
On Tue, Nov 16, 2021 at 8:08 AM Tamás Ozsváth wrote:
> Hi All,
> I tried to compose a protable virtualEnvironment using Python. I aready
> found a solution which already works but still not stable.
> So by creating venv in conventional way, I additionally copy the Python
> executable and related
On Tue, Nov 16, 2021 at 4:46 AM Petr Viktorin wrote:
> On 16. 11. 21 1:11, Brett Cannon wrote:
> >
> >
> > On Sun, Nov 14, 2021 at 3:01 PM Victor Stinner > <mailto:vstin...@python.org>> wrote:
> >
> > On Sun, Nov 14, 2021 at 6:34 PM Eric V. Sm
I put the PEP back on our agenda to discuss this.
On Wed, Nov 17, 2021 at 2:40 PM Guido van Rossum wrote:
> Hi Barry,
>
> That's fantastic news!
>
> Somewhat embarrassingly, on typing-sig we're still discussing one or two
> final tweaks. In particular, the PEP as accepted forbids a certain
> con
This is a personal plea (i.e. not coming from the SC at all), but in the
last month we have had PEPs changed twice post-submission to the SC. That's
a big time sink as we take multiple meetings to discuss a PEP and having
things change underneath us causes us to have to re-evaluate our
discussions
when we are ready again" is helpful to let us know to
simply halt thinking and discussing the PEP.
>
> On Thu, Nov 18, 2021 at 12:04 PM Brett Cannon wrote:
>
>> This is a personal plea (i.e. not coming from the SC at all), but in the
>> last month we have had PEPs changed
On Tue, Nov 30, 2021 at 9:09 AM Steven D'Aprano wrote:
> On Tue, Nov 30, 2021 at 02:30:18PM +, Paul Moore wrote:
>
> > And to be clear, it's often very non-obvious how to annotate something
> > - in https://github.com/pfmoore/editables I basically gave up because
> > I couldn't work out how t
On Tue, Nov 30, 2021 at 1:34 PM Paul Moore wrote:
> On Tue, 30 Nov 2021 at 19:07, Brett Cannon wrote:
> >
> > On Tue, Nov 30, 2021 at 9:09 AM Steven D'Aprano
> wrote:
> >>
> >> On Tue, Nov 30, 2021 at 02:30:18PM +, Paul Moore wrote:
> >>
&
On Wed, Dec 1, 2021 at 10:40 PM Christopher Barker
wrote:
> I know this isn't really the place for this conversation, but:
>
>
>> which is what `os.PathLike` represents, hence why `str` isn't covered by
>> it);
>>
>
> wait, what? It seems so clear to me that "PathLike" (as a type specifier)
> wou
I just pushed an update to PEP 12 which includes a complete PEP template
file.
You can see the file at
https://github.com/python/peps/blob/main/pep-0012/pep-.rst and it is
also embedded in PEP 12 at https://python.github.io/peps/pep-0012/#template
(it will hit the official URL eventually).
___
On Tue, Dec 14, 2021 at 9:41 AM Eric Snow
wrote:
> One of the open questions relative to subinterpreters is: how to
> reduce the amount of work required for extension modules to support
> them? Thanks to Petr Viktorin for a lot of work he's done in this
> area (e.g. PEP 489)! Extensions also ha
On Tue, Dec 14, 2021 at 10:23 AM Eric Snow
wrote:
> Most of the work toward interpreter isolation and a per-interpreter
> GIL involves moving static global variables to _PyRuntimeState or
> PyInterpreterState (or module state). Through the effort of quite a
> few people, we've made good progress
On Sat, Dec 18, 2021 at 4:00 PM Guido van Rossum wrote:
> On Sat, Dec 18, 2021 at 2:16 PM Serhiy Storchaka
> wrote:
>
>> The output of "python -h" is 104 lines long now. It was only 51 lines in
>> 3.6. 35% of it is about the -X option, and 30% about environment
>> variables. Also some lines in t
On Sun, Dec 19, 2021 at 8:26 PM Christopher Barker
wrote:
>
> On 12/18/2021 3:13 PM, Batuhan Taskaya wrote:
>>
>> > tl;dr: I find it very troubling that we are going on a path where need
>> > to increase the language complexity (syntax) only in the cause
>> > 'easier' typing.
>
>
> Which brings u
On Mon, Dec 20, 2021 at 3:44 AM Mark Shannon wrote:
> Hi,
>
> Why not make Callable usable as a function decorator?
>
>
>
> The motivating example in the PEP is this:
>
>
> def flat_map(
> l: list[int],
> func: Callable[[int], list[int]]
> ) -> list[int]:
>
>
>
> Since, as the
As someone with use of this, would you find this useful (i.e. +1, +0)?
Serhiy already said "no" in another thread.
On Mon, Dec 20, 2021 at 4:38 AM Andrew Svetlov
wrote:
> Perhaps Serhiy did more accurate counting, my estimate is very rough.
>
> On Mon, Dec 20, 2021 at 2:15 PM Serhiy Storchaka
>
On Thu, Dec 23, 2021 at 5:13 PM Guido van Rossum wrote:
> On Thu, Dec 23, 2021 at 3:24 PM Steven D'Aprano
> wrote:
>
>> On Thu, Dec 23, 2021 at 02:09:50PM -0800, Guido van Rossum wrote:
>>
>> > Without decorator too (that was Lukasz’ idea). Why bother with the
>> > decorator (*if* we were to go
On Tue, Jan 11, 2022 at 10:40 AM Gregory P. Smith wrote:
>
> On Tue, Jan 11, 2022 at 10:29 AM Guido van Rossum
> wrote:
>
>> I personally think F-strings should not be usable as docstrings. If you
>> want a dynamically calculated docstring you should assign it dynamically,
>> not smuggle it in u
On Tue, Jan 18, 2022 at 9:43 AM Richard Damon
wrote:
>
>
> On Jan 18, 2022, at 11:34 AM, Guido van Rossum wrote:
>
>
> At best it shows that deprecations are complicated no matter how well you
> plan them. I remember that "noisy by default" deprecation warnings were
> widely despised.
>
> On T
On Thu, Feb 3, 2022 at 9:27 AM Victor Stinner wrote:
> Hi Guido,
>
[SNIP]
>
> On Thu, Feb 3, 2022 at 1:40 AM Guido van Rossum wrote:
>
>
[SNIP]
> >
> > Maybe we need to help there. For example IIRC conda-forge will build
> conda packages -- maybe we should offer a service like that for whee
On Thu, Feb 3, 2022 at 6:37 AM Victor Stinner wrote:
> By the way, Argument Clinic now produces way faster calling
> conventions than hand-written METH_VARARGS with PyArg_ParseTuple(). It
> would be make this tool available to 3rd party projects.
>
> Either extract it and put it on PyPI, but it m
On Thu, Feb 3, 2022 at 6:31 AM Victor Stinner wrote:
> On Wed, Feb 2, 2022 at 11:43 PM Eric Snow
> wrote:
> > My plan is to replace our use of _Py_IDENTIFIER() with statically
> > initialized string objects (as fields under _PyRuntimeState). That
> > involves the following:
> >
> > * add a PyUn
On Thu, Feb 3, 2022 at 3:53 PM Eric V. Smith wrote:
> On 2/3/2022 12:15 PM, Victor Stinner wrote:
> > I'm working bottom-to-top: prepare PyObject and PyVarObject to become
> > opaque, *and* top-to-bottom: prepare subclasses (structures
> > "inheriting" from PyObject and PyVarObject) to become opa
On Mon, Feb 7, 2022 at 11:02 AM Victor Stinner wrote:
> Hi Mark,
>
> Aha, good, you posted an email to python-dev, good :-) Last days, I
> was trying to collect more data about this topic, especially find
> platforms which *don't* support IEEE 754, before posting to
> python-dev.
>
> Nowadays, ou
On Mon, Feb 7, 2022 at 12:31 PM Gregory P. Smith wrote:
>
>
> On Mon, Feb 7, 2022 at 11:06 AM Victor Stinner
> wrote:
>
>> Hi Mark,
>>
>> Aha, good, you posted an email to python-dev, good :-) Last days, I
>> was trying to collect more data about this topic, especially find
>> platforms which *d
On Mon, Feb 7, 2022 at 8:59 AM Victor Stinner wrote:
> On Mon, Feb 7, 2022 at 5:48 PM Guido van Rossum wrote:
> > So you're proposing to completely get rid of those three?
>
> I don't propose to remove them, but only call them if Python is built
> in debug mode. Or remove them from the release b
On Mon, Feb 7, 2022 at 4:56 AM Steve Dower wrote:
> On 2/6/2022 4:44 PM, Christian Heimes wrote:
> > If I had the power and time, then I would replace urllib with a simpler,
> > reduced HTTP client that uses platform's HTTP library under the hood
> > (WinHTTP on Windows, NSURLSession (?) on macOS
Can I suggest adding a "Specification" section (see
https://www.python.org/dev/peps/pep-0012/#suggested-sections for the
suggested sections to have in a PEP)?
When you first pull up the PEP it goes from "Rationale" to "Valid Locations
for LiteralString". As a reader that doesn't point me at a vali
1201 - 1300 of 3314 matches
Mail list logo
