[issue12297] Clarifications to atexit.register and unregister doc

2012-02-15 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Thanks. I’ve also realized that the doc does not mention that any callable can be used; I don’t know if we should say it explicitly (I think I did a change like that recently in another file), or if we expect people to just know it from

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-15 Thread Roundup Robot
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 55fc092dad72 by Éric Araujo in branch '3.2': Improve doc for atexit.register and unregister (#12297) http://hg.python.org/cpython/rev/55fc092dad72 New changeset f7163afecb97 by Éric Araujo in branch 'default': Merge

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-15 Thread Roundup Robot
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset a99632426af5 by Éric Araujo in branch '2.7': Improve doc for atexit.register (#12297) http://hg.python.org/cpython/rev/a99632426af5 -- ___ Python tracker

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-15 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Closing as fixed, but if you have any feedback on my function vs. callable question, please share. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-12 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: + This function returns *func* which makes it possible add , after 'func'. +This obviously only works with functions that ... I think I would like this better without 'obviously' (which you inherited). Otherwise, seems good to go to me.

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-11 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: I assume the patch is an improved description of reality. The old 'without binding the original name to ``None``.' is confusing to me in that context, so good riddance. However, I am not familiar with atexit or how it is intended to work. If

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-11 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I wrote the patch after testing in a shell, so I’m confident it describes reality; I was more asking a wording/phrasing review. -- ___ Python tracker rep...@bugs.python.org

[issue12297] Clarifications to atexit.register and unregister doc

2012-02-10 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Maybe one of you gentlemen would like to review this. -- nosy: +ezio.melotti, terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12297

[issue12297] Clarifications to atexit.register and unregister doc

2011-06-09 Thread Éric Araujo
New submission from Éric Araujo mer...@netwok.org: I wanted to know the behavior of atexit.register with the same function added more than once and found out it is not explicitly documented. I experimented and made a patch to the doc. -- assignee: eric.araujo components: