On Mon, Dec 11, 2017 at 12:26 PM R. David Murray
wrote:
> On Mon, 11 Dec 2017 14:56:21 -0500, Donald Stufft
> wrote:
> >
> > > On Dec 11, 2017, at 2:52 PM, R. David Murray
> wrote:
> > >
> > > If 2fa is required for contribution to CPython, I'll stop
> > > contributing.
> >
> > I’m curious why?
On Wed, May 2, 2018 at 2:49 AM, Victor Stinner wrote:
> Hi,
>
> I would like to start a poll on Chris Angelico's PEP 572 "Assignment
> Expressions", restricted to Python core developers, to prepare the
> talk at the Language Summit:
>
>https://www.python.org/dev/peps/pep-0572/
>
> The poll is
VSTS is clearly not yet a stable continuous integration platform. It needs
to be made non-blocking, and AppVeyor and Travis need to be brought back!
Examples:
https://github.com/python/cpython/pull/6938#issuecomment-389908094
Windows broke -
https://python.visualstudio.com/cpython/_build?buil
On Fri, May 18, 2018 at 9:45 AM Terry Reedy wrote:
> On 5/18/2018 12:25 AM, Gregory P. Smith wrote:
> > VSTS is clearly not yet a stable continuous integration platform. It
> > needs to be made non-blocking, and AppVeyor and Travis need to be
> > brought back!
> &
On Fri, May 18, 2018 at 3:28 PM Guido van Rossum wrote:
> Discussing PEPs on python-dev and python-ideas is clearly not scalable any
> more. (Even python-committers probably doesn't scale too well. :-)
>
> I wonder if it would make sense to require that for each PEP a new GitHub
> *repo* be creat
Quick response:
+0.5
My first reaction was "really?" given the amount of iteration required due
to lack of CPython extension module API experience demonstrated in the
os.posix_spawn PRs. (I am not surprised to see Serhiy's negative
reaction) But Pablo shows drive and desire to do good things an
On Thu, Jul 12, 2018 at 12:17 PM Brett Cannon wrote:
> On Thu, 12 Jul 2018 at 11:53 Barry Warsaw wrote:
>
>>
>> That said, I think a triumvirate would work (Guido’s Unworthy Inherited
>> Delegation Organization).
>
>
> Nice! "GUIDO decided ..." Totally going to mess with Guido's personal SEO,
>
On Tue, Oct 9, 2018 at 8:24 PM Jack Diederich wrote:
> I'm worried about the new format combined with governance discussions. As
> best I can tell 51 CPython committers have signed up for an account [I
> think that is a big number, btw] but only 17 have posted anything; That 17
> is about 5 more
Ned - and any release manager in this situation in the future - has a
default valid answer to this request: No.
If we're ever going to do an "EL" or "LTS" Python, that should be decided
and agreed upon *long before the end of its existing planned maintenance
cycle* instead of right as it is ending
On Tue, Feb 12, 2019 at 1:59 PM Antoine Pitrou wrote:
>
> Le 11/02/2019 à 20:00, Barry Warsaw a écrit :
> > On Feb 11, 2019, at 09:48, Victor Stinner wrote:
> >>
> >> tl; dr How can we decide if we should stop using mailing list or if we
> >> should stop using discuss.python.org?
> >
> > Point o
On Wed, Feb 13, 2019 at 12:50 PM Antoine Pitrou wrote:
>
> Le 13/02/2019 à 21:31, Gregory P. Smith a écrit :
> >
> > I know I can browse easily through a 161-message mailing-list or
> > newsgroup thread using a traditional threaded view, read what I want,
> &g
Our pythontestdotnet repo is different than the cpython repo and the
certificate gets pushed to the server after being committed by hand so it's
a synchronization problem,.
https://github.com/python/cpython/pull/13192 should clear it up. It's
awaiting the slow CI queuing gods. It is marked autom
If this cert change is impacting CI checks for everyone's PRs, I suspect
all PRs will need to merge this change into their branch before they can
pass CI.
Having CI depend on external network resources does not seem like a good
idea.
-gps
On Wed, May 8, 2019 at 11:04 AM Antoine Pitrou wrote:
>
Yesterday it failed to produce a backport or tell me that it couldn't
(after the "i'm now working on ..." message was left on the master PR). I
waited a couple hours just in case and ran cherry_picker myself instead.
Same thing today apparently on
https://github.com/python/cpython/pull/13192 assum
fwiw a future way to avoid this mess is in
https://bugs.python.org/issue36855: have the tests support multiple
certificates so we can stage the new ones into our repo before updating the
server.
-gps
On Wed, May 8, 2019 at 11:15 AM Gregory P. Smith wrote:
> If this cert change is impacting
On Mon, May 13, 2019 at 4:11 PM Barry Warsaw wrote:
> On May 13, 2019, at 01:14, Victor Stinner wrote:
>
> > I'm no longer sure myself that I can define them. I prefer to repeat
> > what others say :-) Basically, a core developers is someone who
> > produces commits :-) That's one definition.
>
FWIW that is a configure flag, not a flag to the compiler, so I see no
problem with this. The default build has not changed, it just exposes
another way to build the interpreter. We've done this in the past with
things like --enable-optimizations and such flags.
In this case it appears to enable
On Wed, Apr 8, 2020 at 8:32 PM Dong-hee Na wrote:
>
> I still don't know all the parts of Python interpreter/compiler.
Never fear. None of us do either! =)
welcome!
-gps
___
python-committers mailing list -- python-committers@python.org
To unsubscr
On Wed, Apr 15, 2020 at 6:53 AM Brett Cannon wrote:
> joannah nanjekye wrote:
> > Hey all,
> > Unfortunately this year am too busy and cant even attend the language
> > summit mostly.
>
> :( Sorry to hear that.
>
> > However if I knew the schedule, I could sign up for a session or two
> online.
>
We've got the automerge tag on GH, it+bot make it awesome. There's one more
thing I'd like to see that could help with bug hygiene: A tag to close the
associated bug as "fixed" after the merge happens.
This doesn't have to be tied to automerge; in practice you'd find them used
in unison somewhat o
signs and implements
our GH Issues workflow (PEP-581 and 588 or otherwise).
-gps
>
> Victor
>
> Le dim. 11 oct. 2020 à 21:16, Guido van Rossum a écrit
> :
> >
> > Once issues move to GitHub we’ll have this with no additional effort.
> >
> > On Sun, Oct 11, 202
On Sun, Oct 11, 2020 at 4:23 PM Berker Peksağ
wrote:
> On Sun, Oct 11, 2020 at 10:14 PM Gregory P. Smith wrote:
> >
> > We've got the automerge tag on GH, it+bot make it awesome. There's one
> more thing I'd like to see that could help with bug hygiene: A tag
On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner wrote:
> Hi,
>
> Python has no mandatory Linux CI job on pull requests anymore. Right
> now Windows (x64) remains the only mandatory job. Please be careful to
> manually check other CI before merging a PR.
>
> --
>
> We had to deal with at least 3 di
On Tue, Mar 2, 2021 at 6:44 PM Senthil Kumaran wrote:
> Hello Python Developers,
>
> I notice TLS tests failing in the ssl test suite in master, 3.9 and
> 3.8 branches.
>
> https://github.com/python/cpython/runs/2018191733
>
> Is it to do with infrastructure, certificate? I am unable to determine
For lack of better things to do with that...
https://bugs.python.org/issue43382 filed to track it.
On Tue, Mar 2, 2021 at 7:30 PM Gregory P. Smith wrote:
>
> On Tue, Mar 2, 2021 at 6:44 PM Senthil Kumaran wrote:
>
>> Hello Python Developers,
>>
>> I notice TLS te
On Tue, Mar 16, 2021 at 9:42 AM Christian Heimes
wrote:
> On 16/03/2021 16.54, Julien Palard wrote:
> > Le 2021-03-16 à 15:52, Christian Heimes a écrit :
> >> could you please explain your use case? Which problem are you trying to
> >> solve? How would a sha256 checksum help you solve that proble
We already have https://python.zulipchat.com/ setup.
https://mail.python.org/pipermail/python-dev/2018-April/152826.html
I don't hang around there all the time, but I usually re-open a window
there around pycons and core dev sprints.
-gps
On Thu, May 13, 2021 at 4:53 PM Guido van Rossum wrote:
On Mon, May 17, 2021 at 6:44 PM Kyle Stanley wrote:
>
> FWIW, I would love to add a core dev Discord server to my long-ish list of
>> Discord servers. It's a chat platform I find convenient (much more so than
>> Zulip and Slack, and slightly more so than IRC), very organised, with good
>> moderat
> - Subscriptions may expire for lack of activity, but resubscribing is
welcomed.
This does not mean we *need* to expel people due to inactivity. Lurking is
one method of learning. Manually, I would not bother to try and remove
inactive subscribers until an actual problem arises.
If we do want
On Fri, Mar 11, 2022 at 10:45 AM Brett Cannon wrote:
>
> On Fri, Mar 11, 2022 at 9:16 AM Paul Moore wrote:
>
>> On Fri, 11 Mar 2022 at 17:09, Marc-Andre Lemburg wrote:
>> >
>> > On 11.03.2022 17:42, Zachary Ware wrote:
>> > >
>> > > - Only code which either supports a higher-tier platform or is
On Mon, Mar 14, 2022 at 11:43 AM Marc-Andre Lemburg wrote:
> On 14.03.2022 19:34, Brett Cannon wrote:
> > Greg proposed something like "Code changes to support platforms beyond
> tier1 or
> > tier2 may be rejected, broken, or removed from the CPython codebase
> without
> > notice if they cause a
On Tue, Mar 22, 2022 at 5:02 PM Steven D'Aprano wrote:
> On Tue, Mar 22, 2022 at 04:26:57PM -0700, Brett Cannon wrote:
>
> >1. Update PEP 2 to say a PEP is necessary to add a module to the
> stdlib
> >2. Update PEP 4 to say that a PEP is necessary to deprecate/remove a
> >module
>
> D
On Tue, Mar 22, 2022 at 4:36 PM Barry Warsaw wrote:
> PEP 2 will have to be “un-superseded”, and presumably the devguide (which
> PEP 2 points to) will also need to be updated.
>
we discussed that a bit. the dev guide makes sense as a "how to do it"
purpose document, useful for constructing PRs
On Fri, Apr 1, 2022 at 12:22 PM Brett Cannon wrote:
>
> On Thu, Mar 31, 2022 at 4:40 PM Victor Stinner
> wrote:
>
>> Hi,
>>
>> I don't think that the current PEP 11 draft (*) describes correctly
>> the current status of a bunch of platforms which are not "actively"
>> supported. I like to call t
In-case yesterday's mail got flagged as spam due to being sent from Google
Forms directly to the mailing list (which made it show up marked
"suspicious" even on my end):
I sent out an attendance survey for the CPython Core Dev Sprint this
October 3-7, 2022: https://forms.gle/j5baU9GTQtXpQE578
Pl
free time also means that, if it isn't too much to ask, I have the time to
> "crash" the Python Core Dev Sprint this year. I know I'm very late to the
> party, I can bring my own food and stay away from anything that can't
> handle an extra person. Let me know ple
On Mon, Oct 24, 2022 at 3:59 AM Pablo Galindo Salgado
wrote:
> Hi everyone,
>
> I emerged from cherry-picking hell! As mentioned previously, the 3.11.0
> final release will be done from the "branch-v3.11.0" branch
> and will contain a bunch of cherry-picked commits on top of v3.11.0rc2.
> These c
On Mon, Jan 26, 2009 at 1:59 PM, Matthias Klose wrote:
> Guido van Rossum schrieb:
> > On Mon, Jan 26, 2009 at 1:27 PM, Matthias Klose wrote:
> >> Guido van Rossum schrieb:
> >>> I'm not sure I understand your request. Is it okay to build docs using
> >>> a version of sphinx that is included in
I think those instructions are for merging lots of things at once.
What I've used when I'm merging a single revision is this:
g...@pts/6.dealer/9:46AM% svn up
~/sandbox/python/release26-maint
At revision 70301.
g...@pts/6.dealer/9:47AM% python ../svnmerge.py merge -r70197
property 'svnmerge-integ
i assume someone already knows, just pointing it out.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
On Sun, Sep 13, 2009 at 8:54 AM, Matthias Klose wrote:
> On 06.04.2009 00:33, Matthias Klose wrote:
>>
>> While looking at the diffs between the 261 release tags and the 26 branch,
>> I
>> noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6
>> sections.
>> I moved all of these to 2.
On Sat, Feb 20, 2010 at 12:32 PM, Jeffrey Yasskin wrote:
> Hi all,
>
> David Malcolm is the Fedora maintainer for the Python package and has
> written a gdb plugin to replace and dramatically improve our old
> Misc/gdbinit file using the new python scripting support in gdb-7. You
> can see it in a
On Mon, Mar 1, 2010 at 1:16 AM, Eric Smith wrote:
> Steven Bethard wrote:
>>
>> I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
>> someone remind me again what the commit process is? Commit to 2.7 and
>> merge to 3.2? And do we merge with svnmerge.py or svn merge? There's
>>
On Tue, Apr 6, 2010 at 11:39 AM, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Oracle just released Berkeley DB 5.0.21, with features like SQLite façade.
>
> I am now testing pybsddb 5.0.0, that supports BDB 5.0.x.
>
> My original plan was to delay integration of pybsddb 5
On Mon, Apr 19, 2010 at 4:07 PM, Mark Hammond wrote:
> On 20/04/2010 4:51 AM, Michael Foord wrote:
>>
>> Hello all,
>>
>> I would like to propose Tim Golden as a Python committer. He has been
>> involved in Python for many years, is a capable Windows guy, and has
>> submitted many patches / docume
On Sun, May 9, 2010 at 1:22 PM, Antoine Pitrou wrote:
> Le dimanche 09 mai 2010 à 22:04 +0200, Victor Stinner a écrit :
>> Le dimanche 09 mai 2010 18:56:27, Antoine Pitrou a écrit :
>> > This was done in r81029 (trunk), r81031 (2.6), r81032 (3.x) and r81033
>> > (3.1). I'm mentioning the revision
+1
On May 20, 2010 1:28 PM, "Mark Dickinson" wrote:
I propose that Alexander Belopolsky be given svn commit access. I've
already checked with him that he's interested (he is), and I'm
prepared to mentor him while he's learning the ropes.
A brief history: Alexander's been contributing patches f
+1
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Lib/test/test_subprocess.py
> description:
> Null merge to record previous incorrecly merged changeset from 3.2
>
Thanks. It looks like I did my merge incorrectly, I'll revisit my hg
procedures.
*flogs self*
-gps
> branch:
> changeset: 70465:4f248dd34dd9
> branch: 3
On Mon, Feb 6, 2012 at 2:02 PM, Michael Foord wrote:
>
> On 6 Feb 2012, at 21:55, Brett Cannon wrote:
>
>>
>>
>> On Tue, Jan 10, 2012 at 08:04, Michael Foord
>> wrote:
>> Hello Python Committers,
>>
>> As usual we will hold a Python Language Summit before the PyCon US
>> conference.
>>
>> The l
The fixes for the expat hash randomization DoS are in and working -
http://bugs.python.org/issue14234. New stable and security fix rc2 release
candidates should be created for 2.6, 2.7, 3.1 and 3.2.
Barry and MvL agreed that this weekend should work for them to creating
release builds.
-gps
On Wed, Mar 14, 2012 at 6:35 PM, Benjamin Peterson wrote:
> 2012/3/14 Gregory P. Smith :
> > The fixes for the expat hash randomization DoS are in and working -
> > http://bugs.python.org/issue14234. New stable and security fix rc2
> release
> > candidates should be creat
FYI - there is a network exploitable vulnerability in OpenSSL -
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2110
Our windows builds likely need updating. At the very least make sure
openssl is updated before the next time we produce binaries. Its up to the
release managers if they wa
On Mon, Apr 23, 2012 at 2:42 PM, wrote:
> I don't see any occurrence of these functions in the various versions of
>> the _ssl module.
>> Is Python really affected by this vulnerability?
>>
>
> We use SSL_CTX_use_certificate_chain_**file, which ultimately uses
> d2i_X509_AUX_fp (I think).
>
> Ho
+1
He doesn't already have them? Blink.
--
got tyops? this was quickly tapped out on a touch screen.
On Aug 23, 2012 4:59 PM, "Nick Coghlan" wrote:
> I'd like to propose granting Eric Snow commit privileges.
>
> He's been contributing for a couple of years, mostly working on the
> import system
On Tue, Oct 16, 2012 at 7:44 AM, Chris Jerdonek wrote:
> On Tue, Oct 16, 2012 at 6:32 AM, Eli Bendersky wrote:
> >
> > I had the privilege of joining Google's Mountain View office yesterday,
> and
> > was wondering who else from the core development team works there, or in
> > Google in general (
On Tue, Oct 16, 2012 at 5:06 PM, Anthony Baxter wrote:
> Yep. People tend to stop being so active when they join Google (including
> me) :-(
>
My activity increased. I would not make that statement.
-gps
___
python-committers mailing list
python-commit
On May 24, 2013 2:26 PM, "Benjamin Peterson" wrote:
>
> 2013/5/24 Brett Cannon :
> > It's an extreme example, but for instance I added an entry for this
> > sys.modules change where I just added a clarifying sentence. Probably
> > not needed but wanted to make sure that people got the message they
On May 24, 2013 2:55 PM, "Antoine Pitrou" wrote:
>
> Le vendredi 24 mai 2013 à 16:22 -0400, Brett Cannon a écrit :
> > >
> > > I don't understand why it's painful to backport. Can you explain?
> >
> > If I make a very minor fix to the docs I have to:
> >
> > # In a 3.3 checkout
> > Fix docs
> > Co
On May 25, 2013 1:40 AM, "Nick Coghlan" wrote:
>
> On Sat, May 25, 2013 at 2:01 PM, Eric Snow
wrote:
> > On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
> > wrote:
> >> and it recognizes that users don't really need to look across merge
> >> boundaries.
> >
> > This is tricky though for any p
On May 25, 2013 8:29 AM, "Gregory P. Smith" wrote:
>
>
> On May 25, 2013 1:40 AM, "Nick Coghlan" wrote:
> >
> > On Sat, May 25, 2013 at 2:01 PM, Eric Snow
wrote:
> > > On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
> > > wrote:
&g
On May 26, 2013 1:15 PM, "Brett Cannon" wrote:
>
>
> On May 25, 2013 9:18 PM, "Nick Coghlan" wrote:
> >
> > On Sun, May 26, 2013 at 9:41 AM, Brett Cannon wrote:
> > >> The NEWS update script could even use the revision history to decide
> > >> which order to add entries to the bulleted list.
> >
On Fri, Sep 6, 2013 at 7:30 PM, Antoine Pitrou wrote:
> Le samedi 07 septembre 2013 à 02:03 +0200, Antoine Pitrou a écrit :
> > Hello,
> >
> > I've temporarily reverted hg.python.org to a vanilla Mercurial
> > installation (non-modified) in order to try and eliminate a recent
> > performance prob
On Tue, Jan 7, 2014 at 1:18 PM, Eli Bendersky wrote:
> Hello,
>
> Does it really make sense to introduce large amounts of code churn after
> the release of 3.4 beta2? It started innocently enough, but now it seems
> that the whole implementation is being reconsidered (Antoine's email to
> pydev).
On Tue, Jan 7, 2014 at 4:58 PM, Larry Hastings wrote:
> On 01/07/2014 03:10 PM, A.M. Kuchling wrote:
>
> On Tue, Jan 07, 2014 at 02:37:22PM -0800, Eli Bendersky wrote:
>
> Just to be clear, this is exactly what I mean. I'm not saying AC is not
> worth it; I'm questioning the timing.
>
> Agreed
actually if your patch contains
"diff -r f4377699fd47 Lib/test/test_zipimport.py"
lines prior to the --- line as hg diff can emit, it'll do the right thing
and show the review against the version of the file listed (or at least
against it's branch head? that's an example taken from 3.3 for a patc
+1
On Tue, Jul 8, 2014 at 7:06 AM, Eli Bendersky wrote:
>
>
>
> On Tue, Jul 8, 2014 at 4:18 AM, Victor Stinner
> wrote:
>
>> Hi,
>>
>> Ben Hoyt (benh...@gmail.com) is working on the os.scandir() PEP 471:
>> http://legacy.python.org/dev/peps/pep-0471/
>>
>> Currently, he send me the PEP text an
+1 for commit access, Raymond volunteered as a mentor.
I agree with MAL, it is more beneficial to trust people and give out commit
access early.
-gregory.p.smith
On Sat Jan 10 2015 at 9:16:26 AM Ethan Furman wrote:
> On 01/06/2015 11:09 PM, Raymond Hettinger wrote:
> >
> > I would like to prop
On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
wrote:
> to have to do some extra work to make the hash links work in the bug
> tracker, since I don't think there's any a priori way to distinguish
> between hg hashes and git hashes.
>
Just ignore the remote possibility of short 32-bit hash prefi
On Fri, Mar 4, 2016 at 10:07 PM Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
>
> > On Mar 4, 2016, at 4:07 PM, Brett Cannon wrote:
> >
> > I guess I'm just worried about the health of this project. I'm doing
> what I can through the migration to GitHub to make it easier for others to
>
+1 thanks for mentoring.
On Mon, Nov 21, 2016, 2:14 PM Victor Stinner
wrote:
> Hi,
>
> 2016-11-21 21:53 GMT+01:00 Brett Cannon :
> > We received an email from Xiang with his SSH keys and GitHub username
> > (although no subscription request for python-committers). Was he finally
> > approved for
I do not think we should require individual developers committing changes
to configure.ac to use a particular version of autoconf when regenerating
configure. That is a burden.
The solution to your problem is to maintain your patches _only_ against
configure.ac and rerun autoconf using whatever ve
72 matches
Mail list logo
