PEP 791: edits (address SC feedback)

[skirpichev]

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

---

📚 Documentation preview 📚: https://pep-previews--4639.org.readthedocs.build/

https://pep-previews--4639.org.readthedocs.build/pep-0791/

[skirpichev]

N/B: This extends c_div() example and adds a trivial note that a separate namespace is good also to avoid name conflicts (with example).

I'll wait for more feedback in the d.p.o thread, then make this ready for review.

[vstinner]

You should also update the PEP to use math.integer namespace, no?

[skirpichev]

You should also update the PEP to use math.integer namespace, no?

I'm not sure. IMO, this should be postponed till final resolution of the SC.

On one hand, SC preference was expressed sufficiently clear. On another hand, this will also require adjustment in the implementation. That might be a waste of work.

I think it's clear that it's a minor point and that decision on module naming - left to SC.

[vstinner]

SC expressed a strong preference for math.integer name. I suggest updating the PEP now to make it more likely to be accepted by the SC.

[vstinner]

LGTM.

@skirpichev: Tell me when it's ready to be merged.

[skirpichev]

Tell me when it's ready to be merged.

Oh, forgot to reply. BTW, when my pr is ready to review - it's ready to be merged. On my taste, of course.

[vstinner]

Ok, I merged your PR.

[vstinner]

You may add a comment to python/steering-council#310 and the discussion to say that the PEP has been updated to address SC's feedback.