On 2019-12-26 14:35, Michael wrote:
First - best wishes all for a happy and healthy 2020!
As my nickname implies - my primary means to contribute to Python is
with regard to AIX. One of the things I recently came across is
Misc/README.AIX which was last updated sometime between 2010 and 2014. I
am thinking a facelift is in order. Assuming 2010-2011 as the original
date - much has changed and many of the comments are no longer accurate.
Before saying so, I would like to check here that - having all tests
pass on the 3.8 bot implies that there are no outstanding issues. As to
the historical issues in the current document - these could either be
deleted, or a short text describing when they were resolved (e.g.,
Python 3.7, or just resolved, but noone knows exactly how or when -
whether it was a Python change, or a platform (AIX) change.
Delete them. The README's history is in Git. If you know additional
details (like when an issue was resolved), you can say that in the
commit message.
What I see as being more relevant is the description re: how to build
Python for AIX - for the "do it youself"-ers.
So, besides the direct question re: what to say about the old "known
issues" and whether there are no known issues aka, no issues identified
via the standard tests - I would appreciate feedback on what is
considered appropriate - anno 2020 - for any Misc/README.platform text.
Additionally, I am willing to work on other areas of the standard
documentation where it is either needed or considered appropriate for
platform specific details and/or examples.
This is not something I would try to get done in a single PR, Instead I
am thinking a single -longer term- issue - and multiple PR's to work
through corrections and additions during 2020. Focus on Python 3.9 and
beyond yet where appropriate backlevel to Python 3.8 or even 3.7.
Sincerely,
Michael
Some devs have been setting GitHub repositories for larger projects,
with issues (TODO lists), collaboration, wikis or even blog-like
documentation. For example:
https://github.com/ericsnowcurrently/multi-core-python
https://faster-cpython.readthedocs.io/
https://github.com/python/typing
https://github.com/python/asyncio
It helps to have a space where you can focus on a task without having to
prove that "this is good for CPython right now" *all* the time.
You could replace README.AIX text with a link there. Afterwards, I think
the devguide or Python documentation could link to such a space for the
AIX build instructions; then, when finalized, the instructions
themselves could be in Python docs or in a new README.AIX. But I do
recommend to separate writing the text from proposing it for inclusion
in CPython.
_______________________________________________
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/Y4I7CDFIRD7H64THTMHWWHIJ7GCXEWSH/
Code of Conduct: http://python.org/psf/codeofconduct/
