, 2020 at 7:25 PM Rob Cliffe via Python-Dev
mailto:python-dev@python.org>> wrote:
TLDR: In os.scandir directory entries, atime is always a copy of
mtime
rather than the actual access time.
Demo program: Windows 10, Python 3.8.3:
# osscandirtest.py
import time,
On 19.10.2020 14:47, Steve Dower wrote:
On 19Oct2020 1242, Steve Dower wrote:
On 15Oct2020 2239, Rob Cliffe via Python-Dev wrote:
TLDR: In os.scandir directory entries, atime is always a copy of mtime rather
than the actual access time.
Correction - os.stat() updates the access time to
//babeljs.io/blog/2017/09/11/zero-config-with-babel-macros
https://github.com/kentcdodds/babel-plugin-macros
https://github.com/jgierer12/awesome-babel-macros
That's a general intro, the code repo for the macro plugin, and a repo
that lists implemented macros.
Martin
________
On 19/10/2020 12:42, Steve Dower wrote:
On 15Oct2020 2239, Rob Cliffe via Python-Dev wrote:
TLDR: In os.scandir directory entries, atime is always a copy of
mtime rather than the actual access time.
Correction - os.stat() updates the access time to _now_, while
os.scandir() returns the
into a strong reference as soon as
possible.
Ronald
—
Twitter / micro.blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/
>
> /arry
>
> * Unfortunately, I used my last wish back in February, wishing I could spend
> more time at home.
>
> _
lt in fairly significant changes
to the core interpreter, and it might be hard to find enough core devs that
willing and able to review
changes in a timely manner.
Ronald
_______
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an emai
ed if we still wanted to maintain the Solaris support in
> Python, because Solaris buildbots were failing for longer than 6
> months and nobody was able to fix them. It was requested to find a
> core developer volunteer to fix Solaris issues and to set up a Solaris
> buildbot.
>
&
/ micro.blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/ <https://blog.ronaldoussoren.net/>
>
> On Fri, 30 Oct 2020, 09:29 Ronald Oussoren via Python-Dev,
> mailto:python-dev@python.org>> wrote:
>
> > On 29 Oct 2020, at 22:43, Victor Stinner > <ma
s been out of development for over 14 years
(https://en.wikipedia.org/wiki/IRIX <https://en.wikipedia.org/wiki/IRIX>).
Ronald___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
htt
blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/
>
> Regards
>
> Rajesh Narasimhan
> _______________
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org
___
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-dev@python.org
to regular tuple unpacking. If I read the PEP
correctly binding the same name multiple times is also forbidden in more
complex scenario’s where multiple binding is not so easily recognised, such as
"case Rect(Point(x, y), Size(x, w))”.
Ronald
—
Twitter / micro.blog: @ronaldoussoren
Blog:
i start with or work on.
___
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
source.
Sent from my iPhone
> On Oct 30, 2020, at 4:59 PM, Gregory P. Smith wrote:
>
>
>
>> On Fri, Oct 30, 2020 at 2:30 PM Garrett D'Amore via Python-Dev
>> wrote:
>> I’m not on this list. But I have offered to help - if there are tasks that
>> ne
ial; but
in the meantime, I would kindly ask you to be very careful and conservative
about deleting information solely for "didactic" reasons.
thanks a lot
riccardo polignieri
___________
Python-Dev mailing list -- python-dev@python.org
the tutorial is the only
place
where some concepts are presented in a discursive way ... even if not
"beginner friendly".
All in all, although I understand that the tutorial should be completely
revised,
I would still recommend the utmost caution especially when deleting
informa
t;),
just as it is now. And, that if you start removing things, on the one hand
you are not doing beginners a favor big enough, while you might be damaging
(even if only scratching) something useful for others.
best,
r.
___
Python-Dev mailing list -- pyt
would personally wait until having 3+ opinions prior to merging any
> removals (...)
Thanks for this. Besides, I can see from the Git log that the tutorial is
indeed
seldom updated anyway, which is a pity on the one hand, a relief on the other.
best,
riccardo
_____
the tutorial. Now, this would be a deletion that I would welcome.
I suspect there are quite a few (relatively) low hanging fruits like this one
out there.
best,
riccardo
_______________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send a
e unfriendly, highly technical reference guide or to a
> PEP.
Indeed. The PEPs are the worst, more often than not. I remember when I first
learned Pyhton,
every time the documentation linked to a PEP, I felt a shiver down my spine.
r.
___________
Pyth
isting.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
___
Python-Dev mailing list --python-dev@python.org
To unsubscribe send an email topython-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Messa
that could be better spent on other issues.
If you (the current SC) were actually accepting PEP 634, would the vote be the
same? Then accept it, and let's all move on.
--
~Ethan~
_______
Python-Dev mailing list -- python-dev@python.org
To unsubscri
a 3.8.7 release blocker or a trigger for
> a special 3.8.8 release shortly thereafter?
Ronald
—
Twitter / micro.blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an emai
ches and I have the technical
> competency to perform the backport. If you need help, I could potentially
> find time to hack on it. Just email me privately (or ping @indygreg on
> GitHub) and let me know. Even if they don't get into 3.8.7, I'll likely
> cherry pick the pat
015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________
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/
Messa
ork. For 3.7 and earlier this will never work, those branches are closed for
development.
Ronald
—
Twitter / micro.blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/
>
> --
> Greg
> ___________
> Python-Dev mailing list -- python-de
is competitive with other
state-of-the-art memory collectors.
"""
https://www.microsoft.com/en-us/research/uploads/prod/2020/11/perceus-tr-v1.pdf
___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email t
particular way.
In short: a test named `assertSequenceEqual` should, I would think,
work for any sequence and therefore (based on the available documentation)
should not depend on the class-specific implementation of __eq__.
Is that wrong?
Thank you, Alan Isaac
________
ac
On 12/22/2020 2:28 PM, Ivan Pozdeev via Python-Dev wrote:
You sure about that? For me, bool(np.array) raises an exception:
In [12]: np.__version__ Out[12]: '1.19.4'
In [11]: if [False, False]==np.array([False, False]): print("foo") <...> ValueError: The truth va
In the light of this and https://github.com/python/cpython/blob/6afb730e2a8bf0b472b4c3157bcf5b44aa7e6d56/Lib/unittest/case.py#L970 (linked
to from https://mail.python.org/archives/list/python-dev@python.org/message/AQRLRVY7EJT4LTOCV7CLOFK3FJJTVYYM/ )
I reckon that
*like the other code before
On 22.12.2020 22:59, Ivan Pozdeev via Python-Dev wrote:
In the light of this and https://github.com/python/cpython/blob/6afb730e2a8bf0b472b4c3157bcf5b44aa7e6d56/Lib/unittest/case.py#L970 (linked
to from https://mail.python.org/archives/list/python-dev@python.org/message
> On 25 Dec 2020, at 23:03, Nelson, Karl E. via Python-Dev
> wrote:
>
> I was directed to post this request to the general Python development
> community so hopefully this is on topic.
>
> One of the weaknesses of the PyUnicode implementation is that the type is
>
On 26/12/2020 10:52, Ronald Oussoren via Python-Dev wrote:
On 25 Dec 2020, at 23:03, Nelson, Karl E. via Python-Dev
wrote:
I was directed to post this request to the general Python development
community so hopefully this is on topic.
One of the weaknesses of the PyUnicode implementation is
> On 26 Dec 2020, at 18:43, Guido van Rossum wrote:
>
> On Sat, Dec 26, 2020 at 3:54 AM Phil Thompson via Python-Dev
> mailto:python-dev@python.org>> wrote:
> It's worth comparing the situation with byte arrays. There is no problem
> of translating different
d compare both type and value.
Paul
___________
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-dev@python.org/mess
______
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-dev@python.org/message/D4LABINWQ6ZF
On 28/12/2020 02:07, Inada Naoki wrote:
On Sun, Dec 27, 2020 at 8:20 PM Ronald Oussoren via Python-Dev
wrote:
On 26 Dec 2020, at 18:43, Guido van Rossum wrote:
On Sat, Dec 26, 2020 at 3:54 AM Phil Thompson via Python-Dev
wrote:
That wouldn’t be a solution for code using the PyUnicode_
tion, it must not be a unicode object at all.
I would have thought that an object was defined by its behaviour rather
than by any particular implementation detail. However I completely
understand the desire to avoid additional complexity of the
implementation.
Phil
______
Twitter / micro.blog: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/ <https://blog.ronaldoussoren.net/>
_______
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 ar
dress this kind
of issue?
___
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
ers
some django official documents
some python official documents
but i don't know how to use my learnings from books
If you help me to know how I can study in the right way ,I will appreciate you
for my whole life
thank you and happy new year :)
______
Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
_______
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
Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
_______________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.o
;R(206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev
> On 8 Jan 2021, at 20:38, Chris Barker via Python-Dev
> wrote:
>
> Sorry if I'm out of the loop here, but with Apple's new chip coming out, we
> need new a build configuration (which I think has already been started, if
> not done).
>
> Perhaps we cou
within that
scope.
Paul
_______
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/pytho
tanza from
> the end too.
> Welcome to the world, baby 649!
>
> /arry
> _______
> 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-de
k in Python, so I'm not the guy
> to ask how possible / hard this would be. Then again, the
> implementation of closures is obscure enough that I've never been
> able to understand them, so that seems to establish at least a base
> level of difficulty.
> Anyway, one of the conce
on, class, module, etc. are being defined.
> That's what PEP 563 is referring to. If you read the thread from
> November 2017 where the idea was discussed, they were talking about
> referring to e.g. "class-level definitions", as in, things defined
> inside class scope.
; That would work, but I think the API is a bit of a code smell.
> __annotations__ would no longer be stable:
> > a.__annotations__ = o
> > assert a.__annotations__ == o
> Would that assert fail? It depends on what type(o) is, which is
> surprising.
Equally surprising?:
a.__c
nts() twice, and near
> > as I can figure out, localns is literally only ever set to None
> > unless you override it with the parameter.
> >
>
>
> This seems to be a bug in get_type_hints() for which someone should
> file a bug on bpo, please!
___
;t be marshalled.
Since the __co_annotations__ function will get globals from the
function it annotates, doesn't it get more than just module scope?
Paul
_______
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to p
speak.
Conversation has already started here [1] and here [2].
[1]: https://bugs.python.org/issue42843
[2]: https://github.com/python/cpython/pull/24142
--
[Julien Palard](https://mdk.fr)
___________
Python-Dev mailing list -- python-dev@python.org
To u
only recently, so not
using that is a reasonable suggestion.
I support keeping same Sphinx version across all the supported python versions.
This is not a sustainable route since this way, there's no way to change the
version at all.
--
Senthil
_______
t; and "type(None)".
> > >
> > Huh, I wasn't aware of that.
> >
>
> This has tripped up many people. Maybe we should just bite the bullet
> and change this?
+1, FWIW.
___________
Python-Dev mailing list -- python
On 13.01.2021 3:12, Senthil Kumaran wrote:
On Wed, Jan 13, 2021 at 02:53:30AM +0300, Ivan Pozdeev via Python-Dev wrote:
I support keeping same Sphinx version across all the supported python versions.
This is not a sustainable route since this way, there's no way to change the
version a
ostpone the Sphinx upgrade, no worries.
--
[Julien Palard](https://mdk.fr)
_______
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 archi
y doable for a few years to ease the migration, we could
even keep Sphinx 1.8 support for a few years as it still works with
those two "fixes" applied (it would imply reopening
https://bugs.python.org/issue36675 but I'm not against it).
--
[Julien Palard](https://mdk.fr)
_______
to 3.2 for Python 3.10? Or would it be
better to keep Sphinx 2 compatibility for a few years (how many?) before
requiring Sphinx 3?
Bests,
--
[Julien Palard](https://mdk.fr)
_______
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send
6-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
_______
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.o
ien Palard](https://mdk.fr)
_______
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/l
still be "optimised" away?
Thanks
Rob Cliffe
_______
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
> On 14 Jan 2021, at 23:03, Chris Barker via Python-Dev
> wrote:
>
> Ned,
>
> Thanks -- I'll take further discussion to the python-mac list.
>
> Ronald:
>
> That’s a feature of the framework build. The unix build is exactly the same
> as a unix bui
d
> value, in that cached values get deleted when they're out-of-date.
> (An observation that may provide some guidance if we decide to rename
> __co_annotations__.) This idiom may be familiar to the user--unlike
> your proposed semantics, which I don't recall ever seeing used
nnotations__. If you're not even aware that it exists, it's
> not mysterious ;-)
>
> Cheers,
>
> /arry
___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.
ew
> annotations() function to hide the details. It wouldn't
> be the same as get_type_hints(), since it wouldn't make
> any assumptions about what the annotations mean.
>
___________
Python-Dev mailing list -- python-dev@python.org
To u
Thanks Ronald,
This is really helpful.
-CHB
On Fri, Jan 15, 2021 at 5:43 AM Ronald Oussoren
wrote:
>
>
> On 14 Jan 2021, at 23:03, Chris Barker via Python-Dev <
> python-dev@python.org> wrote:
>
> Ned,
>
> Thanks -- I'll take further discussion to the pyth
CHB
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
___
be a different implementation of this function. I’ve looked into this
in the past for macOS, and that platform
has an API to retrieve the size of the stack as well as a pointer to the start
of the stack (AFAIK stacks aren’t auto-growing
on macOS)
Ronald
—
Twitter / micro.blog: @ronal
was decided to include "helper" modules like "_aix_support" which
is used by sysconfig. But test modules like _testcapi are excluded to
make the list shorter (it's rare to run the CPython test suite outside
Python).
There are 83 private modules, name starting with an undersc
s no way to verify a
module's contents, either.
As such, there's no way to tell if any given module being imported is a
standard or a 3rd-party one.
On 25.01.2021 20:33, Chris Jerdonek wrote:
On Mon, Jan 25, 2021 at 7:51 AM Ivan Pozdeev via Python-Dev mailto:python-dev@python.org>>
Fortunately for, you :) , all this argument is not against the feature per se but only against its use to blindly filter module lists for
automated bug reports.
On 26.01.2021 1:34, Victor Stinner wrote:
On Mon, Jan 25, 2021 at 11:22 PM Ivan Pozdeev via Python-Dev
wrote:
That's not pos
unions. All useful features.
Is there a good reason not to start using C11 now?
Cheers,
Mark.
___________________
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/pyth
a C extension type
with its own tp_new?
Thanks,
Phil
___________
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://mai
On 01/02/2021 23:50, Greg Ewing wrote:
On 2/02/21 12:13 am, Phil Thompson via Python-Dev wrote:
TypeError: object.__new__(B) is not safe, use B.__new__()
It's not safe because object.__new__ doesn't know about any
C-level initialisation that A or B need.
But A.__new__ is call
Phil
On Mon, Feb 1, 2021 at 3:27 AM Phil Thompson via Python-Dev <
python-dev@python.org> wrote:
Hi,
I'm trying to understand the purpose of the check in tp_new_wrapper()
of
typeobject.c that results in the "is not safe" exception.
I have the following class hierarchy
rstand
why __new__ has this particular requirement.
Phil
_______________
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 a
ct type-wise.
Thanks for the explanation.
Phil
___________
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.p
g the
interpreter.
Adding these extremely complex instructions would be a big backward step.
Cheers,
Mark.
___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman
_future__ due to its contentious
nature met immediate resistance. No point going down that road.
Kind regards,
Steve
On Sat, Feb 6, 2021 at 8:15 PM Ivan Pozdeev via Python-Dev mailto:python-dev@python.org>> wrote:
With such a large new area of functionality that's at odds with existing
On 07.02.2021 0:24, Paul Sokolovsky wrote:
Hello,
On Sun, 7 Feb 2021 00:00:41 +0300
Ivan Pozdeev via Python-Dev wrote:
Who said "__future__"?
Other people said __future__. And yet other said "it's ok the way it
is, it's better to have it like that then keep not
Hi Python Dev team,
I submitted a PR https://github.com/python/cpython/pull/23736 two months ago.
The PR, which fixes an issue https://bugs.python.org/issue41928 in ZipFile, is
"awaiting core review".
Best regards.
Andrea Giudiceandrea
_______
___
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-dev@python.org
and avoiding featuritis.
___________
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/pyth
Terry Reedy wrote:
> I nosied and requested a review from the active zipfile 'expert' (Serhiy).
Thank you Terry.
Regards.
Andrea
___________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@pyt
egards,
--
Regards,
Ivan
_______
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/arch
nse them all at once and be done with it?
In fact, this whole thread feels like removing 80%-complete translations
from a program because they 'burden developers' and confuse users. Even
if the translations are not actively updated and degenerates with
strings changing, some users find the
ame with a concrete working solution, and so emails are still
read manually one by one. Also, almost nobody is trying to fix tests
which are failing randomly.
For example, I called multiple times for help to fix test_asyncio, so
far it's still randomly every day:
* 2020:
https:/
s issue at last!
Likewise, half of the bullet points in https://mail.python.org/archives/list/python-dev@python.org/message/LJ3E2UQBPDSFEH7ULNF3QVOYEQYRSAGI/
comes from either ppl trying to bypass the process, or the release manager doing others' jobs that should've already been done had t
.
A reference implementation (unreviewed) can be found at:
https://github.com/iritkatriel/cpython/pull/10
Thank you for your help
Kind regards
Irit, Yury & Guido
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to py
anything intelligent
about.
If it wishes to handle them, you need to split MultiError into a separate library that anyone could use without having to pull the entire
`trio`.
On 23.02.2021 3:24, Irit Katriel via Python-Dev wrote:
Hi all,
We would like to request feedback on PEP 654 -- Exception Gr
ect that there will be a need for blanket
migrations of "except T" to "except (T, ExceptionGroup)" to "except *T".
Irit
_______
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@
ption from the PEP on how to handle this kind of pattern,
> especially for code that must support multiple versions of Python, would be
> extremely helpful.
>
> Damian
>
>>
>>
_______
Python-Dev mailing list -- python-dev@python.org
To u
up('', (NotADirectoryError(20, 'The directory
name is invalid'),))
There is no need for it to always raise ExceptionGroup. It can propagate
the user's exception as is if it has no exceptions to add. But the caller
needs to assume that it may raise an ExceptionGroup, and use
ubgroup(lambda e: not predicate(e))
> assert g1 == h1 and g2 == h2 # only true if `None not in {g1, g2}`
> ```
>
An empty subgroup should also return None. I see this is not mentioned in
the PEP, so I will add it. Thanks.
Irit
___
Python-Dev m
ction:
> the PEP adds a better way how it could have been designed, and that is
> virtuous. Still, having it in Motivation might be misleading.
>
I agree. Raising ExceptionGroups is an API breaking change, for any
library.
No function should just start raising ExceptionGroups.
> l
rno.EPIPE) from None
_______
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/l
Those are quite different directions.
___________
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/archive
split() currently copies (context, cause, traceback) from the original
ExceptionGroup to the new ones. We could have some protocol, but I'm not
sure what it would look like. I'm pretty sure there will be a cost, and I'm
not sure I understand why no subclassing is a serious enough l
distinction between code that raises
ExceptionGroups and code that doesn't. Any code can propagate them, like
any code can raise any other exception.
Does this mean that more code needs to be aware of the possibility of them
showing up? Is that a problem? Maybe this a simpler state of affairs
o
401 - 500 of 939 matches
Mail list logo
