On 03. 11. 21 2:58, Kyle Stanley wrote:
I'd suggest both: briefer, easier to read write up for average user in
docs, more details/semantics in informational PEP. Thanks for working on
this, Petr!
Well, this is the brief write-up :)
Maybe it would work better if the info was integrated into the relevant
parts of the docs, rather than be a separate HOWTO.
I went with an informational PEP because it's quicker to publish.
On Tue, Nov 2, 2021 at 2:07 PM David Mertz, Ph.D. <[email protected]
<mailto:[email protected]>> wrote:
This is an amazing document, Petr. Really great work!
I think I agree with Marc-André that putting it in the actual Python
documentation would give it more visibility than in a PEP.
On Tue, Nov 2, 2021, 1:06 PM Marc-Andre Lemburg <[email protected]
<mailto:[email protected]>> wrote:
On 01.11.2021 13:17, Petr Viktorin wrote:
>> PEP: 9999
>> Title: Unicode Security Considerations for Python
>> Author: Petr Viktorin <[email protected]
<mailto:[email protected]>>
>> Status: Active
>> Type: Informational
>> Content-Type: text/x-rst
>> Created: 01-Nov-2021
>> Post-History:
Thanks for writing this up. I'm not sure whether a PEP is the
right place
for such documentation, though. Wouldn't it be more visible in
the standard
Python documentation ?
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Experts (#1, Nov
02 2021)
>>> Python Projects, Coaching and Support ...
https://www.egenix.com/ <https://www.egenix.com/>
>>> Python Product Development ...
https://consulting.egenix.com/ <https://consulting.egenix.com/>
________________________________________________________________________
::: We implement business ideas - efficiently in both time and
costs :::
eGenix.com Software, Skills and Services GmbH
Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
https://www.egenix.com/company/contact/
<https://www.egenix.com/company/contact/>
https://www.malemburg.com/ <https://www.malemburg.com/>
_______________________________________________
Python-Dev mailing list -- [email protected]
<mailto:[email protected]>
To unsubscribe send an email to [email protected]
<mailto:[email protected]>
https://mail.python.org/mailman3/lists/python-dev.python.org/
<https://mail.python.org/mailman3/lists/python-dev.python.org/>
Message archived at
https://mail.python.org/archives/list/[email protected]/message/FSFG2B3LCWU5PQWX3WRIOJGNV2JFW4AU/
<https://mail.python.org/archives/list/[email protected]/message/FSFG2B3LCWU5PQWX3WRIOJGNV2JFW4AU/>
Code of Conduct: http://python.org/psf/codeofconduct/
<http://python.org/psf/codeofconduct/>
_______________________________________________
Python-Dev mailing list -- [email protected]
<mailto:[email protected]>
To unsubscribe send an email to [email protected]
<mailto:[email protected]>
https://mail.python.org/mailman3/lists/python-dev.python.org/
<https://mail.python.org/mailman3/lists/python-dev.python.org/>
Message archived at
https://mail.python.org/archives/list/[email protected]/message/6PHPDZRCYNA44NHSHXPBL7QMWXMHXWGU/
<https://mail.python.org/archives/list/[email protected]/message/6PHPDZRCYNA44NHSHXPBL7QMWXMHXWGU/>
Code of Conduct: http://python.org/psf/codeofconduct/
<http://python.org/psf/codeofconduct/>
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/6OET4CKEZIA34PAXIJR7BUDKT2DPX2DG/
Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/ZNANXZ7VP6CVDAGWEFXHKYFO6AR3MZXQ/
Code of Conduct: http://python.org/psf/codeofconduct/