➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2006-04-18 16:48 by bethard, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| peps_0359_3002.patch | bethard, 2006-04-18 16:48 | Updates to PEPs 359 and 3002 | ||
| Messages (4) | |||
|---|---|---|---|
| msg50066 - (view) | Author: Steven Bethard (bethard) *  |
Date: 2006-04-18 16:48 | |
I don't have commit access to the peps directory, so here are some updates to PEPs 359 and 3002. |
|||
| msg50067 - (view) | Author: David Goodger (goodger) |
Date: 2006-04-18 19:43 | |
Logged In: YES user_id=7733 In future, please send PEP updates to the PEP editors (peps@python.org). |
|||
| msg50068 - (view) | Author: Steven Bethard (bethard) * |
Date: 2006-04-18 20:00 | |
Logged In: YES user_id=945502 Will do. I guess PEP 1 probably needs updated - it says: """ For more mature, or finished PEPs you may want to submit corrections to the SourceForge bug manager [11] or better yet, the SourceForge patch manager [6] so that your changes don't get lost. """ It also mentions some stuff about CVS which is presumably no longer accurate. |
|||
| msg50069 - (view) | Author: David Goodger (goodger) |
Date: 2006-04-18 20:31 | |
Logged In: YES user_id=7733 I didn't realize that PEP 1 recommended the SF trackers (although the PEPs in question are neither mature nor finished ;-). I'd say it's OK to use SF, but be sure to assign the patch to a PEP editor (I don't always catch every new patche & bug report). I'll update PEP 1. I believe this is the first time anyone has gone this route. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:16 | admin | set | github: 43242 |
| 2006-04-18 16:48:15 | bethard | create | |