> So how about making PY_SSIZE_T_CLEAN not mandatory in Python 3.11?
> Extension modules can use '#' format with ssize_t, without
> PY_SSIZE_T_CLEAN defined.
> Or should we wait one more version?
Hi, Inada,
I suggest we should wait until at least Python 3.12 or Python 4.0.
There have an another q
Eric Snow wrote:
> In practice neither has been a problem over the years. However, it
> does make discovery a bit more complicated, both for new contributors
> and for tools. So I consider it at the least worth looking into the
> value (and downsides, if any) of moving the seemingly out-of-place
hose module is
builtinmodules, so they have no __file__ attribute and listed in PYTHON_OBJS(I
am not sure I understand clearly). But I have no clear criteria what module
should be putted in python directory or modules directory. I found some core
developer have mentioned this detail 13 years
Hi,
I notice some modules not in modules directory(for example:
_warnings、marshal in python directory). Do we need port those modules to
modules directory?
Sorry for my noisy info.
Bests Wishs,
Hai Shi
___
Python-Dev mailing list -- python-dev
Wow, congratulations:)
Looking forword to Marcel' PRs:
https://github.com/python/cpython/compare/master...Dormouse759:pep-c-rebase_newer
ps: two days ago, I asked what blocked pep-0573 privately ;)
___
Python-Dev mailing list -- python-dev@python.org
To
Wow, congratulations!
ps: two days ago, I asked petr what blocked PEP-573 privately(mch extension
module need this pep ;))
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.pyth
