Software Foundation.
https://www.python.org/psf/
Your friendly release team,
Ned Deily @nad
Steve Dower @steve.dower
Pablo Galindo Salgado @pablogsal
Łukasz Langa @ambv
Thomas Wouters @thomas
___
python-committers mailing list -- python-committers
my mistakes are not too obvious to end users :P
Being your release manager for 3.11 and 3.10 has been a privilege and an
honor (and it will continue for a couple
of years of bugfixes and security releases, I'm not going anywhere).
Regards from rainy London,
Pablo Galindo Sa
hon
Software Foundation.
https://www.python.org/psf/
If you have any questions, please reach out to me or another member of the
release team :)
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Gali
cts so the SHAs may change (maybe that’s why GitHub shows that
message).
> On 24 Oct 2022, at 16:59, Gregory P. Smith wrote:
>
>
>
> On Mon, Oct 24, 2022 at 3:59 AM Pablo Galindo Salgado <mailto:pablog...@gmail.com>> wrote:
> Hi everyone,
>
> I emerged
se commits* and let me know ASAP if we are missing
something you would like to include on the 3.11.0 final release.
You have until 15:00 UTC+0 today to let me know, otherwise, your changes
will need to wait until 3.11.1.
Thanks for your help!
Regards from sunny London,
Pablo
core dev team. Also,
funny party hats will be used!
I hope you find the event interesting and consider attending. Python 3.11
is going to be a fantastic release and we want it to be even better :)
Please, reach out to me if you have any questions or suggestions.
Regards from rainy London,
Pablo Ga
g/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/pyt
ly if something
major is discovered we will include it in 3.11.0). So if you have any
bugfix or similar that you want to get included in 3.11.0
please let me know ASAP otherwise, it will need to wait for 3.11.1.
Thank you very much for your help!
Regards from cloudy London,
Pablo Galindo Sa
or another member of the
release team :)
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablog
ganization contributions to the Python
Software Foundation.
https://www.python.org/psf/
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u
on.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
SHA256 (python-3.11.0b5-amd64.exe) =
0cf9d582da862f2fe207fd54b81dfca110e8f04f4b05ab8c3228ce1ea060c7af
SHA256 (python-3.11.0b5-arm64.exe) =
a71efd9d3835d493d8207
BSD-style checksum format hashes for the release artefacts:
SHA256 (python-3.11.0b4-embed-arm64.zip) =
272c6bb4948c597f6578f64c2b15a70466c5dfb49f9b84dba57a84e59e7bd4ef
SHA256 (python-3.11.0b4-amd64.exe) =
a3514b0401e6a85416f3e080586c86ccd9e2e62c8a54b9119d9e6415e3cadb62
SHA256 (python-3.11.0b4-maco
e.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@pyt
from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message a
r
concerns.
Thanks, everyone for your help and understanding and thanks a lot to all of
you for your great work!
Cheers from cloudy London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email
be an outstanding release thank to all of you :)
Cheers from cloudy London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mai
help a lot!
Please, add me as a reviewer to any PR that needs to be merged to address
these issues.
Thanks for your help!
Regards from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe
through organization contributions to the Python
Software Foundation.
https://www.python.org/psf/
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.py
hon.org/psf/
If you have any questions, please reach out to me or another member of the
release team :)
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.py
rds from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message
e new releases!
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
https://www.python.org/psf/
Regards from chilly London,
I should have started this email with "Nobody expects the Spanish
inquisition" :)
On Fri, 6 May 2022 at 13:13, Pablo Galindo Salgado
wrote:
> Hi everyone,
>
> Today we need to start the release of Python 3.11 beta 1. Currently, we
> have the following blockers:
>
>
are addressed and we can continue with the release.
Please, add me as a reviewer to any PR that needs to be merged to address
these issues or any other change that *absolutely needs to go into beta 1*.
Thanks for your help!
Regards from sunny London,
Pablo Galindo Salgado
Is an undetermined time on Friday, that makes it more exciting :)
On Thu, 5 May 2022 at 16:27, Paul Ganssle wrote:
> Is this AoE time or London time?
>
> My last set of changes is kinda coming down to the wire 😬
>
> On May 5, 2022 10:02:46 AM UTC, Pablo Galindo Salgado
> wro
Hi Ethan,
Sorry for the late reply (I was travelling back from PyCon and recovering
from the jet lag)!
Feature freeze is still scheduled for Friday, 2022-05-06. If there are
release blockers or other problems it may take some extra days but I will
announce it here and probably block the main bran
Hi everyone,
I have opened a poll to promote Erlend Aasland as a core developer. Please
read more and vote here:
https://discuss.python.org/t/vote-to-promote-erlend-aasland/15246/2
Thank you!
Regards from sunny London,
Pablo Galindo Salgado
Hi everyone,
We have approximately one month until feature freeze and for 3.11.0b1 to be
released. I wanted to take this time to share some planning
and considerations with you. Please, read carefully these points as they
are important.
* 3.11.0b1 is scheduled for Friday, 2022-05-06, which is aft
faster. More updated benchmarks will be
published on beta 1.
Apologies for the confusion.
Pablo Galindo Salgado
On Wed, 6 Apr 2022 at 11:29, Pablo Galindo Salgado
wrote:
> Br. do you feel that? That's the chill of *beta freeze* coming
> closer. Meanwhile, your friendly CPy
Br. do you feel that? That's the chill of *beta freeze* coming
closer. Meanwhile, your friendly CPython release team doesn’t
rest and we have prepared a shiny new release for you: Python 3.11.0a7.
*
ditions
that are included in the release. This could be
done personally by the release manager or coordinated by them.
If you have any questions, please reach out to me (or any other release
manager if you want) and we will be happy
to answer them :)
Regards from sun
There are no easy releases these days! :sweat: After a week of delay due to
several release blockers, buildbot problems and pandemic-related
difficulties here is 3.11.0a6 for you to test.
https://www.python.org/downloads/release/python-3110a6/
**This is an early developer preview of Python 3.11**
rt them, but for the
> time being the release is on hold, sadly.
>
> Regards from rainy Salamanca,
> Pablo Galindo Salgado
>
> On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado
> wrote:
>
>> Hi everyone,
>>
>> Unfortunately, we have some issues marked as
, sadly.
Regards from rainy Salamanca,
Pablo Galindo Salgado
On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado
wrote:
> Hi everyone,
>
> Unfortunately, we have some issues marked as release blockers that are
> holding the 3.11.0a6 release.
> Some of these issues have been solved but
.
Regards from sunny Salamanca,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org
On 03/02/2022 11:27 pm, Pablo Galindo Salgado wrote:
> > We needed to tame some angry buildbots, but after a small fight, we won
> with just some scratches! Here you have a shiny new alpha release: Python
> 3.11.0a5.
> >
> > https://www.python.org/downloads/release/python-3
We needed to tame some angry buildbots, but after a small fight, we won
with just some scratches! Here you have a shiny new alpha release: Python
3.11.0a5.
https://www.python.org/downloads/release/python-3110a5/
**This is an early developer preview of Python 3.11**
# Major new features of the 3.
pull requests
until these issues are fixed. Please, ping me if you have a pull request
for fixing any of these
issues so we can merge.
I apologize for the inconvenience.
Thanks for your understanding,
Regards from rainy London,
Pablo Galindo Salgado
> Is there a possible middle ground here? Rather than a required PR check
(or a full buildbot run), maybe we could just add a new “magic” label that
runs a single refleak job using the GitHub actions runners.
That sounds like a good compromise and it will be strictly better than the
current setup.
>
> > It is nigh impossible to pick out errors in a PR from flaky tests,
> flaky machines and pre-existing errors.
I agree with the sentiment but is certainly not that dramatic. We (people
watching the build bots) do it on a regular basis, and many contributors do
it very efficiently as well. I a
Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https
from cloudy London,
Pablo Galindo Salgado
On Tue, 4 Jan 2022 at 23:12, Pablo Galindo Salgado
wrote:
> Hi everyone,
>
> I am writing this to notify you that unfortunately the release of 3.11.0a4
> is blocked as there are a bunch of release blockers
> (some of them affect Python 3
://bugs.python.org/issue43683
If this was a single release blocker I would think about moving forward but
unfortunately, there are several of them and one of
them is that Python fails to compile FreeBSD, so I am halting the release
until these are fixed.
Regards from rainy London,
Pablo Galindo Salgado
You can tell that we are slowly getting closer to the first beta as the
number of release blockers that we need to fix on every release starts to
increase [image: :sweat_smile:] But we did it! Thanks to Steve Dower, Ned
Deily, Christian Heimes, Łukasz Langa and Mark Shannon that helped get
things r
organization contributions to the Python
Software Foundation.
https://www.python.org/psf/
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
Now that we are on a release spree, here you have the first alpha release of
Python 3.11: Python 3.11.0a1. Let the testing and validation games begin!
https://www.python.org/downloads/release/python-3110a1/
*Major new features of the 3.11 series, compared with 3.10*
Python 3.11 is still in devel
!
Thank you all, your work really makes a difference.
Regards from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org
community https://www.python.org/psf/donations/.
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
___
Python 3.10 is one month away, can you believe it? This snake is still
trying to bite as it has been an interesting day of fighting fires, release
blockers, and a bunch of late bugs but your friendly release team always
delivers :)
You can get this new release while is still fresh here:
https://w
udy London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
ht
cted this for future
releases.
If you had any problem building docs with the previous release artifacts
for 3.10.0rc1, please try again.
Regards from cloudy London,
Your friendly release team,
Pablo Galindo @pablogsal
Ned Deily @nad
Steve Dower @steve.dower
On Tue, 3 Aug 2021 at 17:31, Pablo Ga
Python 3.10.0 is almost ready. This release, 3.10.0rc1, is the penultimate
release preview. You can get it here:
https://www.python.org/downloads/release/python-3100rc1/
*This is the first release candidate of Python 3.10*
This release, **3.10.0rc1**, is the penultimate release preview. Enterin
copy-and-paste change,
everything requires peer review from a core developer.
(You can find these instructions and details in the devguide
<https://devguide.python.org/devcycle/#rc>).
Thank you all for your help!
Regards from rainy London,
Pablo Galindo Salgado
_
Wow! A release on a Saturday? Do the release management team even rest? You
better believe it, because this is the last of the planned beta releases.
This means that the next pre-release will be the first release candidate of
Python 3.10.0. Remember that our goal is to have no ABI changes after thi
Summer is almost here (at least in half of the planet) and Python 3.10 is
finishing baking in the oven. For those of you that want to taste it before
is finally ready (and if you are a library developer, you certainly do!)
you can have the second-to-last beta now, but be careful as is still very
ho
After fighting with some release blockers, implementing a bunch of GC
traversal functions, and fixing some pending reference leaks, we finally
have Python 3.10.0 beta 2 ready for you! Thanks to everyone that helped to
unblock the release!
https://www.python.org/downloads/release/python-3100b2/
#
> So, on what principled basis do we exempt, say, ints from
participating in cyclic GC too? Do we have to "just know" that a cycle
can't be reached from an int's type object? If so, is that even true?
Or just convenient to pretend to believe to avoid adding 16 more bytes
to each int object and gros
Tim, check this out:
>>> import re, gc
>>> x = re.compile("x")
>>> gc.get_referents(x.__class__)[-1]
That seems due to:
https://github.com/python/cpython/blob/e90e0422182f4ca7faefd19c629f84aebb34e2ee/Objects/typeobject.c#L4241
On Thu, 27 May 2021 at 20:15, Tim Peters wrote:
> [Tim]
> >> And
811#issuecomment-747788766
On Thu, 27 May 2021 at 20:24, Pablo Galindo Salgado
wrote:
> > Can you flesh this out for what stumbled into being my running
> example? That is, how could a regexp pattern object be part of a
> cycle?
>
> Let me try to remember when we saw this problem in the
> Can you flesh this out for what stumbled into being my running
example? That is, how could a regexp pattern object be part of a
cycle?
Let me try to remember when we saw this problem in the past, but
on first sigh, it seems that indeed that cannot happen in the regular case.
> And, in general,
Sorry, the last link should have been:
https://bugs.python.org/issue43908
On Thu, 27 May 2021 at 19:41, Pablo Galindo Salgado
wrote:
> > Modules dicts are cleared during interpreter shutdown to break
> such cycles.
>
> That is precisely what's not working because of t
at C level and then only until they are fully initialized
(PyType_Ready() called).
Check https://bugs.python.org/issue43916
On Thu, 27 May 2021 at 19:38, Marc-Andre Lemburg wrote:
> On 27.05.2021 20:20, Pablo Galindo Salgado wrote:
> >> And if a type pointer is the only thing bein
> "Why?" is baffling to me: how could they possibly participate in a
cycle?
If the type object is a heap type (by default mutable), someone could just
add a reference directly to it that makes it being in a cycle with the
instance.
Even if that's not the case, IIRC, as the type refers to the modu
> So all those instances have an increase in memory footprint
compared to Python 3.7 ?
I am afraid that's the case. This is one of the costs of making types not
being heap types.
On Thu, 27 May 2021, 19:04 Marc-Andre Lemburg, wrote:
> On 27.05.2021 19:40, Tim Peters wrote:
> &g
> And if a type pointer is the only thing being visited, then there's no
point unless the object can itself be reachable from the type object.
But that could happen easily for heap types as they are mutable by default.
For instance, you set the instance in a global:
type -> module -> globals ->
Hi Marc,
Yes, check out this from the 3.9 what's new document:
https://docs.python.org/3/whatsnew/3.9.html#changes-in-the-c-api
Instances of heap-allocated types (such as those created with
PyType_FromSpec() and similar APIs) hold a reference to their type object
since Python 3.8. As indicated i
M, Pablo Galindo Salgado wrote:
>
> Hi,
>
> Friendly reminder that the Python3.10 beta 2 is still blocked on:
>
> https://bugs.python.org/issue42972
>
> Thanks for your help,
>
> Regards from stormy London,
> Pablo Galindo Salgado
>
>
> I took a quick loo
Hi,
Friendly reminder that the Python3.10 beta 2 is still blocked on:
https://bugs.python.org/issue42972
Thanks for your help,
Regards from stormy London,
Pablo Galindo Salgado
On Mon, 24 May 2021 at 23:54, Pablo Galindo Salgado
wrote:
> Small correction:
>
> https://bugs.p
/all/#/builders/693/builds/21
https://buildbot.python.org/all/#/builders/677/builds/22
https://buildbot.python.org/all/#/builders/669/builds/22
...
You can access the release dashboard for the buildbots here:
https://buildbot.python.org/all/#/release_status
On Mon, 24 May 2021 at 23:45, Pablo
ta release.
Thanks for your help,
Regards from stormy London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/li
Congratulations, Irit!
On Tue, 11 May 2021 at 06:18, Brett Cannon wrote:
> EOM
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman
thon 3.10.
Thanks for helping to make Python3.10 a great release.
Regards from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
ht
have some urgent fix or PR that you absolutely need
to get merge before
feature freeze, you can add me as a reviewer to said PR so we can evaluate
the merge.
Thanks for your understanding.
I will update once master is unblocked again.
Regards from cloudy London, Pablo Galindo Salgado
vious
communication about how this will be done and how you should
proceed
https://mail.python.org/archives/list/python-...@python.org/thread/QWW7KGBW5UH2N5FOZOFXQBQPYELWQM3O/
)
If you have any questions or concerns, please contact me as soon as
possible.
Regard
you have any questions or concerns, please contact me as soon as
possible.
Regards from sunny London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers
him bug triage permission. I
will continue mentoring him and I will send him
instructions on how to triage bugs and links to the relevant sections of
the devguide. I ask him to ask me before closing bugs
for the first weeks.
Congrats Ken Jin ✨ 🍰 ✨!
Regards from sunny London,
Pablo Galindo Salgado
> This is one of the several reasons that I don't like using the PR
description as the commit message when using auto-merge :).
I think this is a good motivation to use
https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
instead as you
Your friendly release team,
Pablo Galindo Salgado @pablogsal
Ned Deily @nad
Steve Dower @steve.dower
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.pytho
thanks from the whole Python Steering Council,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python
g
the concerts raised.
Congratulations, Christian!
With thanks from the whole Python Steering Council,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@pytho
ally.
On Thu, 11 Mar 2021, 07:37 Serhiy Storchaka, wrote:
> 10.03.21 16:06, Pablo Galindo Salgado пише:
> > # What you need to do?
> >
> > You just need to update your local clone after the branch name changes.
> > From the local clone of the repository on a compute
d help them update within this timescale.
>
> Has this analysis been published anywhere? I know there are lots of places
> where discussions/documentation happens
>
> Thanks
>
> Steve
>
>
>
> On Wed, Mar 10, 2021 at 2:10 PM Pablo Galindo Salgado
> wrote:
>
>>
un the following commands to update the name of the default branch.
$ git branch -m master main
$ git fetch origin
$ git branch -u origin/main main
Apart from that, you should update any local script or command that uses
the name "master" to use the name "ma
ip Thorne to imagine traversable wormholes
created by holding the "throat" of a Schwarzschild wormhole open with
exotic matter (material that has negative mass/energy).
Regards from rainy London,
Pablo Galindo Salgado
___
python-committers mail
as negative mass/energy).
Regards from rainy London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/li
neutron star or black hole. Those with masses up to the limit remain stable
as white dwarfs. The currently accepted value of the Chandrasekhar limit is
about 1.4 M☉ (2.765×1030 kg). So we can be safe knowing that our sun is not
going to become a black hole!
Re
London,
Pablo Galindo Salgado
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
isingly, the movement of a test particle in such spacetime is not
only a very chaotic system but also has some fractals
<https://arxiv.org/abs/gr-qc/9502014> hiding the complexity of its movement.
Regards from cold London,
Pablo Galindo Salgado
___
It's starting to get very cold (at least on the Northern hemisphere) so we
have been carefully packaging a total of three new Python releases to keep
you warm these days!
Python 3.9.1 is the first maintenance release of Python 3.9, and also the
first version of Python to support macOS 11 Big Sur n
Correction:
> Guido and I have opened a poll to promote Batuhan Taşkaya as a core
developer.
is just me the one proposing the promotion (copy-paste error), although
Guido had the same idea as you can see in the thread :)
Pablo Galindo Salgado
On Fri, 30 Oct 2020 at 10:30, Pablo Gali
Hi everyone,
Guido and I have opened a poll to promote Batuhan Taşkaya as a core
developer. Please read more and vote here:
https://discuss.python.org/t/vote-to-promote-batuhan-taskaya/5592
Thank you!
Regards from cloudy London,
Pablo Galindo Salgado
> We should simply mark the github actions "Tests / Ubuntu" CI as required.
+1 I completely agree with everything Gregory said.
On Fri, 16 Oct 2020 at 19:36, Gregory P. Smith wrote:
>
>
> On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner
> wrote:
>
>> Hi,
>>
>> Python has no mandatory Linux CI j
18:58, Chris Jerdonek
wrote:
> MOn Wed, Oct 14, 2020 at 8:03 AM Pablo Galindo Salgado <
> pablog...@gmail.com> wrote:
>
>> > Would it be possible rerun the tests with the current
>> setup for say the last 1000 revisions or perhaps a subset of these
>> (e.g. every
because
the micro-benchmarks published in the What's new of 3.9 were confusing a
lot of users that
were thinking if 3.9 was slower.
On Wed, 14 Oct 2020 at 15:14, Antoine Pitrou wrote:
>
> Le 14/10/2020 à 15:16, Pablo Galindo Salgado a écrit :
> > Hi!
> >
> > I have
ing :)
That's why from now on I am trying to invest in daily builds for master,
so we can answer that exact question if we detect regressions in the future.
On Wed, 14 Oct 2020 at 15:04, M.-A. Lemburg wrote:
> On 14.10.2020 16:00, Pablo Galindo Salgado wrote:
> >> Would it be possible
on/pyperformance/blob/master/pyperformance/benchmarks/bm_unpack_sequence.py
>
> https://github.com/python/pyperformance/blob/master/pyperformance/benchmarks/bm_regex_dna.py
>
> Thanks.
>
> On 14.10.2020 15:16, Pablo Galindo Salgado wrote:
> > Hi!
> >
> > I have updat
ssumed I'd misread
> the figures, and moved on, but maybe I was wrong to do so...
>
> Paul
>
> On Wed, 14 Oct 2020 at 14:17, Pablo Galindo Salgado
> wrote:
> >
> > Hi!
> >
> > I have updated the branch benchmarks in the pyperformance serve
s" and "Timeline" tabs (
https://speed.python.org/timeline/).
* Once the daily builds are working as expected, I plan to work on trying
to automatically comment or PRs or on bpo if
we detect that a commit has introduced some notable performance regression.
Regards from sunny Lond
As someone that went through doing a release just now and now what it
entailsthanks a lot for all the work, Larry! :)
On Mon, 5 Oct 2020 at 19:39, Barry Warsaw wrote:
> They say being a Python Release Manager is a thankless job, so the Python
> Secret Underground (PSU), which emphatically do
Hi everyone,
Guido and I have opened a poll to promote Lysandros Nikolaou as a core
developer. Please read more and vote here:
https://discuss.python.org/t/vote-to-promote-lysandros-nikolaou/4445
Thank you!
Regards from cloudy London,
Pablo Galindo Salgado
Hi,
I am giving triage privileges to Lysandros Nikolaou (lys.nikolaou on bpo,
lysnikolaou in GitHub) .
Lysandros has been working with Guido and myself in PEP 617 for quite a
long time, being an indispensable
member of the team. In all this time he has proven to have a great set of
technical skil
1 - 100 of 115 matches
Mail list logo
