Hi Terry,
Thanks for your message!
> Then how will modules that customizes traceback presentation, such as
idlelib, be able to get the 4-tuple for a particular traceback entry?
>From the exception, you can get the code object and from the code object
the extra information using
the Python API:
Also, notice we are extending the traceback module (in Python) to support
this, so you probably can also leverage those changes so you don't need to
mess with code objects yourself :)
On Wed, 30 Jun 2021 at 22:29, Pablo Galindo Salgado
wrote:
> Hi Terry,
>
> Thanks for your messa
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
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
__
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
One of the most important things is that I was **not informed** about how
this affects the release
process and we ended up with a venv packaged in the tarball, unfortunately.
I agree that these changes should be notified to the release manager,
precisely to avoid these situations.
I am trying to
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
for everyone that wants to deal with the
grammar or the parser.
Hope that you find it useful :)
P.S. Thanks to everyone that helped with the review!
Regards from cloudy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
> If creating a fake frame is a common use case, we can maybe write a
public C API for that.
I don't think we should think on those terms. We certainly don't want to be
on a case
where yet again we cannot change the internals because we have an official
C-API exposed.
> For example, I saw parser
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
ar
Tell me what you think.
P.S. If you are interested to help with this project, please reach out to
me. If we decide to go ahead we can use your help! :)
Regards from cloudy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.
.. 2}"
'3'
>>> f'{1 +
... 2}'
'3'
On Mon, 20 Sept 2021 at 13:52, Serhiy Storchaka wrote:
> 20.09.21 14:18, Pablo Galindo Salgado пише:
> > * The parser will likely have "\n" characters and backslashes in
> > f-strings expressions,
wrote:
> > On 9/20/2021 7:18 AM, Pablo Galindo Salgado wrote:
> >
> >> there are some interesting things we **could** (emphasis on could)
> >> get out of this and I wanted
> >> to discuss what people think about them.
> >>
> >> * The par
>> But I also think this means we definitely have to get a parser module
What is in this context a "parse" module? Because that will massively
change depending who you ask. We already expose APIs that return AST
objects that can be used for all sort of things and a tokenizer module that
exposes so
>> What do you envision tokenize.py will do with f-strings after this?
It will emit new tokens: FSTRING_START FSTRING_MIDDLE '{' NAME
FSTRING_FORMAT '}' FSTRING_END
On Tue, 21 Sept 2021 at 12:50, Anders Munch wrote:
> Pablo Galindo Salgado [mailto:pablog...@gmai
Hi Erik,
My first question is whether anyone is working on this as well (or
> hasalready done so and I missed it), to avoid duplication of effort.
We have already done this work. This was a contribution by Matthieu
Dartiailh:
https://github.com/we-like-parsers/pegen/blob/main/data/python.gram
> What is the annoyance? What is different between frozen and not frozen?
One interesting consequence of what Eric mentioned (They have a different
loader and repr. Also, frozen modules do not
have __file__ set (and __path__ is always []).) is that frozen modules
don't have a `__file__` attribute
to me if you have any question or suggestion.
Regards from very rainy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lis
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
___
!
Thank you all, your work really makes a difference.
Regards from sunny London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists
Just my two small cents: soft keywords have a cost as they make everything
around them more complicated in
the parser. For example, creating custom error messages around soft
keywords is one or two levels of magnitude
more complicated as sometimes you need to parse segments of
syntactically invalid
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
ython to python calls:
https://github.com/python/cpython/pull/28488
This could explain why the performance is closer to the current master
branch as you indicate:
It gets about the same average performance as the “main” branch of CPython
> 3.11 as of early September 2021.
Cheers from cloudy Lon
As far as I understand we should get a smaller improvement on single thread
because some of the optimizations listed in this work are partially or
totally implemented.
This is excluding any non linear behaviour between the different
optimizations of course, and assuming that both versions yield th
Steering Council met with Ezio to discuss his progress with the
GitHub migration project. The SC advised Ezio as to what the priority
projects are.
Regards from cloudy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To
I am glad you like it :)
I have been told that this is a very popular improvement. I promise to keep
looking for similar things in the future!
Regards from cloudy London,
Pablo Galindo Salgado
On Fri, 29 Oct 2021, 18:23 Steven D'Aprano, wrote:
> I was using Python 3.10 and got this N
to happen with python-dev. The group is
inclined to
accept 649 but there is no clear path on how to handle the transition so
community
discussion is needed.
Regards from rainy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev
I agree with Serhiy's analysis.
On Mon, 29 Nov 2021 at 17:10, Serhiy Storchaka wrote:
> 29.11.21 18:36, Victor Stinner пише:
> > You should consider "no longer have to justify why it's not optimized"
> > as a clear benefit of making this change :-) This optimization is
> > proposed once a year f
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
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
Thanks, Mark for the catch! I have updated it in the release page and all
announcements where I can edit the text :)
On Thu, 9 Dec 2021 at 12:34, Mark Shannon wrote:
>
>
> On 08/12/2021 11:51 pm, Pablo Galindo Salgado wrote:
>
> > * The [Faster Cpython Project](https://github.
One thing to consider: ideally, inmortal objects should not participate in
the GC. There is nothing inheritly wrong if they do but we would need to
update the GC (and therefore add more branching in possible hot paths) to
deal with these as the algorithm requires the refcount to be exact to
correct
All singletons do, AFAIK. And most static types that I can think of also
do, even the empty tuple.
On Wed, 15 Dec 2021 at 16:49, Eric Snow wrote:
> On Wed, Dec 15, 2021 at 2:50 AM Pablo Galindo Salgado
> wrote:
> > One thing to consider: ideally, inmortal objects should not part
>> It does seem a bit silly to actually be tracking that refcount :-)
Not that silly. It can easily help in C extensions to detect wrong DECREF
calls:
>> import ctypes
>> non = ctypes.c_long.from_address(id(None))
>> non.value = 10
>>
Fatal Python error: none_dealloc: deallocating None
Python run
you have any questions or you need help, feel free to ping me in GitHub
if you want.
Regards from rainy London,
Pablo Galindo Salgado
On Mon, 20 Dec 2021, 18:27 Gabriele, wrote:
> Hi there
>
> I hope you would indulge me in asking for some details about the new
> CFrame structure, even
y way or form as this code can and will
likely change a lot (even between patch versions if we found bugs).
Regards from rainy London,
Pablo Galindo Salgado
On Mon, 20 Dec 2021, 21:43 Gabriele, wrote:
> Brandt, Guido, Pablo
>
> Many thanks for your helpful answers. Indeed I'm askin
://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
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
/pep-679-allow-parentheses-in-assert-statements/13003
as I will not be monitoring answers to this thread.
Thanks, everyone for your time!
Regards from cloudy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe
Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python
We considered using colours and other markers such as bold text, but that
opens a considerable can of worms with detecting in all systems and
configurations if that can be done. I have been told that some of these
situations are quite tricky and is not as easy as checking for tty support.
If someo
> On 1/18/2022 7:59 PM, Pablo Galindo Salgado wrote:
> > We considered using colours and other markers such as bold text, but
> > that opens a considerable can of worms with detecting in all systems and
> > configurations if that can be done. I have been told that some of these
.
As I said, I think I would be supportive of considering adding a check for
the full line, but I think that adding more complexity here is quite
dangerous.
On Tue, 18 Jan 2022 at 21:49, Patrick Reader <_...@pxeger.com> wrote:
> On 18/01/2022 20:41, Pablo Galindo Salgado wrote:
>
>
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
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.
> Should there be a getter/setter for co_positions?
We consider the representation of co_postions private, so we don't want
(for now) to ad
getters/setters. If you want to get the position of a instruction, you can
use PyCode_Addr2Location
On Wed, 9 Feb 2022 at 16:22, Petr Viktorin wrote:
> On
).
On Wed, 9 Feb 2022 at 17:38, Stefan Behnel wrote:
> Pablo Galindo Salgado schrieb am 09.02.22 um 17:40:
> >> Should there be a getter/setter for co_positions?
> >
> > We consider the representation of co_postions private
>
> Yes, and that's the issue.
>
That is on pourpose and is the public API for Python. In Python it returns
an iterable of tuples,
which is processed from the actual internal form.
On Wed, 9 Feb 2022 at 18:56, Victor Stinner wrote:
> On Wed, Feb 9, 2022 at 5:48 PM Pablo Galindo Salgado
> wrote:
> > We
allocators are concerned about
memory, not tracing or anything else that can be done by overriding them.
That's why there is no "notify allocator" APIs in the python allocators.
Regards from rainy London,
Pablo Galindo Salgado
On Tue, 15 Feb 2022, 13:57 Sümer Cip, wrote:
rg where this can be
discussed and (maybe) implemented. Please, feel free to add me to the issue
once open :)
Regards from rainy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to pyt
.org/dev/peps/pep-0654/>.
- The SC had an overview of unresolved issues: definition/rules for the
standard library, split in communication channels and the situation
regarding type annotations with PEP 563 and 649.
- The new SC decided to use discord as a new communication c
.
Regards from sunny Salamanca,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https
, 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
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
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**
eturn no sooner than May
>> with the regularly scheduled bug fix releases of 3.9 and 3.10.
>>
>> <https://discuss.python.org/t/python-3-10-4-and-3-9-12-are-now-available-out-of-schedule/14568#we-hope-you-enjoy-the-new-releases-1>We
>> hope you enjoy the new release
You may want to check PEP 603, which more or less proposes this (the author
of the pep is the author of the HAMT code)
check https://peps.python.org/pep-0603/
Alternatively, there is already a pypi package with this code:
https://pypi.org/project/immutables/
Regards from cloudy London,
Pablo
O
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.
*
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
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
> This section of major new features should've included the addition of
atomic groups/possessive matching into the `re` module. This is a boost in
regex matching performance when the pattern doesn't need any backtracking.
Can you provide a bpo number, please?
On Wed, 6 Apr 2022 at 13:15, Jeremiah
I will consider adding it, but I am not sure it qualifies as a "major
feature". I will think about it :)
On Wed, 6 Apr 2022 at 13:38, Jeremiah Vivian
wrote:
> > Can you provide a bpo number, please?
> bpo-433030
> ___
> Python-Dev mailing list -- pytho
dexed access to it (there is a precedent to this in how
we handled updating os.stat_result). I personally
find this quite confusing but it certainly works. There may be other
options.
What do you think?
Cheers from sunny London,
Pablo Galindo Salgado
___
rtainly do.
On Sun, 17 Apr 2022, 20:40 MRAB, wrote:
> On 2022-04-17 18:20, Pablo Galindo Salgado wrote:
> > Hi,
> >
> > We are currently debating in gh-88116
> > (https://github.com/python/cpython/issues/88116
> > <https://github.com/python/cpython/issues/88116&g
As it has been mentioned there is no guarantee that your variable will even
be finalized (or even destroyed) after the frame finishes. For example, if
your variable goes into a reference cycle for whatever reason it may not be
cleared until a GC run happens (and in some situations it may not even b
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
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:
>
>
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,
Done in all places that I can edit! Thanks for the catch :)
On Sun, 8 May 2022 at 09:14, Oleg Iarygin wrote:
> - python-announce@, python-committers@, python-list@
>
> > report issues found to [the Python bug tracker](https://bugs.python.org)
> as soon as possible
>
> The template needs to be up
05-08 04:22, Pablo Galindo Salgado wrote:
> > We did it, team!! After quite a bumpy release process and a bunch of
> > last-time fixes, we have reached **beta 1** and **feature freeze**. What
> > a ride eh? You can get the shiny new release artefacts from here:
> >
>
I have updated it a while ago but it may take some time for the CDN to drop
the cache. Thanks for heads up!
On Sun, 8 May 2022 at 19:08, Mats Wichmann wrote:
> On 5/7/22 21:22, Pablo Galindo Salgado wrote:
>
> > We **strongly encourage** maintainers of third-party Python projects t
In addition, test_exceptions test a bunch of syntax errors and related
locations.
On Tue, 10 May 2022 at 06:41, Serhiy Storchaka wrote:
> 10.05.22 08:10, Venkat Ramakrishnan пише:
> > I'm wondering if there's a repository of test cases that
> > test the Python grammar. Any help would be apprecia
Could you share with us some of the context of what are you trying to
achieve? That way we can offer more specialized help :)
On Tue, 10 May 2022 at 15:50, Venkat Ramakrishnan <
venkat.archit...@gmail.com> wrote:
> Presuming I am looking at the right link?:
> https://github.com/python/cpython/tre
That's used as a literal '/' to make positional-only arguments work. For
example:
lambda x, y, /, z: x+y+z
On Tue, 10 May 2022 at 17:11, Venkat Ramakrishnan <
venkat.archit...@gmail.com> wrote:
> I am looking at:
> https://docs.python.org/3/reference/grammar.html
>
> in which the following defin
There is no *public* one but there is a private one accesible from Python I
added for testing purposes.
On Mon, 30 May 2022, 15:17 Victor Stinner, wrote:
> On Mon, May 30, 2022 at 1:40 AM Eric V. Smith wrote:
> > python -m tokenize < file-to-parse.py
> >
> > See the comment at the top of tokeni
nch, or would
> you be willing to share the code?
> On 30/05/2022 16:23, Pablo Galindo Salgado wrote:
>
> There is no *public* one but there is a private one accesible from Python
> I added for testing purposes.
>
> On Mon, 30 May 2022, 15:17 Victor Stinner, wrote:
>
>>
rds from sunny London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.py
You may be able to work around this issue by preventing pytest to rewrite
the assert statements by adding `--assert=plain` to the command line
invocation until we have beta 3 next month.
On Tue, 31 May 2022 at 23:57, Jean Abou Samra wrote:
> Hi,
>
>
> Le 31/05/2022 à 15:31, P
I have added a small note in the release announcements. Thanks for raising
this with us!
On Wed, 1 Jun 2022 at 00:13, Jean Abou Samra wrote:
>
>
> Le 01/06/2022 à 00:02, Pablo Galindo Salgado a écrit :
> > You may be able to work around this issue by preventing pytest to
> &g
> On 01. 06. 22 0:02, Pablo Galindo Salgado wrote:
> > You may be able to work around this issue by preventing pytest to
> rewrite the
> > assert statements by adding `--assert=plain` to the command line
> invocation
> > until we have beta 3 next month.
>
> That&#x
Just for the heads up: I have sent an email to the release team and we are
considering the proposal. Thanks for raising this with us.
On Tue, 31 May 2022 at 23:39, Pablo Galindo Salgado
wrote:
> > Wouldn't it be more practical to bite the bullet and release b3
> immediately with t
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
Update: we have decided to release Python 3.11.0b3. Let's hope this one is
free of the curse :)
On Wed, 1 Jun 2022 at 07:38, Miro Hrončok wrote:
> On 01. 06. 22 0:39, Pablo Galindo Salgado wrote:
> > > Wouldn't it be more practical to bite the bullet and release b3
>
Hi Robin,
The correct range requirements are mandatory from beta 2. There will be 2
more betas after beta 3: beta4 and beta5.
Please, check out the release announcement for beta3.
Cheers,
Pablo Galindo Salgado
On Fri, 3 Jun 2022, 09:56 Robin Becker, wrote:
> On 01/06/2022 16:58, Pa
se but we likely will
be happy to do small changes if there is something small that we do that is
preventing the use case.
Cheers from cloudy London,
Pablo Galindo Salgado
On Mon, 6 Jun 2022 at 15:38, Gabriele wrote:
> Hi there
>
> I hope you don't mind me sharing my experie
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
> or has at least agreed to, not sure any releases have happened since I
asked).
I did:
https://www.python.org/downloads/release/python-3110b3/#:~:text=3.11.0b3%20is%20the%20second,support%20the%20new%20feature%20release
.
On Mon, 6 Jun 2022 at 19:13, Steve Dower wrote:
> +1. Glad it's not just
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-Dev mailing list -- python-dev@python.org
To unsubscribe send an email
be an outstanding release thank to all of you :)
Cheers from cloudy London,
Pablo Galindo Salgado
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/p
Additionally, I am considering pushing the full release some months in the
future to allow for more betas, given
how unstable 3.11 is currently.
Pablo Galindo Salgado
On Mon, 4 Jul 2022 at 15:26, Miro Hrončok wrote:
> On 24. 06. 22 14:25, Pablo Galindo Salgado wrote:
> > Hi everyone,
&
ing
so we may require more
betas.
Thanks for your understanding,
Pablo Galindo Salgado
On Mon, 4 Jul 2022 at 18:21, Petr Viktorin wrote:
> On 04. 07. 22 19:03, Miro Hrončok wrote:
> > On 04. 07. 22 18:53, Pablo Galindo Salgado wrote:
> >> Hi Miro,
> >>
> >&g
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-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to pyt
e.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/m
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
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
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
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
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
g/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.
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
101 - 200 of 243 matches
Mail list logo
