On 6/2/2021 7:59 PM, Ethan Furman wrote:
On 5/27/21 8:24 PM, Ethan Furman wrote:
> So, like the enum.unique decorator that can be used when duplicate
names should be an error,
> I'm adding a new decorator to verify that a Flag has no missing
aliased values that can be
> used when the programme
On 5/27/21 8:24 PM, Ethan Furman wrote:
> So, like the enum.unique decorator that can be used when duplicate names
should be an error,
> I'm adding a new decorator to verify that a Flag has no missing aliased
values that can be
> used when the programmer thinks it's appropriate... but I have no
I like the idea but I don't understand the full impact yet.
That's my job to assess.
For my research, I was also trying to have a similar compatibility hack for
the changes I have had to do
to allow GC integration.
> This project only targets extension modules written in C by using
> directly the
On Thu, Jun 3, 2021 at 2:30 AM Joannah Nanjekye
wrote:
> Is HPy ready yet given IIRC, there is no even first release yet? I stand to
> be corrected.
> I reckon it will still go through a period of incompatible changes for some
> time/months too.
HPy is a great project, but even if 90% of top 40
Hi,
What do you think of promoting the pythoncapi_compat project that I'm
introducing below in the "C API: Porting to Python 3.10" section of
What's New In Python 3.10?
Should this project be moved under the GitHub psf organization to have
a more "future proof" URL?
I would like to promote this
On Thu, May 27, 2021 at 8:30 PM Ethan Furman wrote:
> But what if we have something like:
>
> class Color(Flag):
> RED = 1# 0001
> BLUE = 4 # 0100
> WHITE = 7 # 0111
>
> As you see, WHITE is an "alias" for a value that does not exist
