On Wed, Oct 04, 2000 at 02:58:25PM +1100, Mark Hammond wrote: [ Mark wants to apply a patch that prevents crashes on windows when loading extentions linked with old Python DLLs, but doesn't know where to document it: PEP 42 or the bug report(s) ] [ Skip proposes a separate PEP ] [ Mark doesn't have time to write a PEP ] > So given this, what should I do - just check it in, and leave it to the > collective memory? ;-) PEP 42 is the meaning of life PEP, meaning that it's everything that needs to be done before python-dev can rest in pieces. I don't think that a solved issue is in its place there, even if it had such a section. A PEP on its own would probably be the best spot, because even if it's a 'temporary' solution now, we or someone else might need the info later. And a PEP doesn't have to be that hard to write ;) And besides, you don't have to be the person to write the PEP, someone else can. And if noone suitable volunteers, perhaps a checkin-message giving 'full' documentation, the necessary sourcecode comments and a reference to both in the bugreport message will suffice... But I'm willing to PEPify whatever docs or comments you write on this issue, Mark. I will need some guidance on what exactly is the issue, but I'm sure I'll get that from one of you Windows lovers ! :-) And no, I don't think Python should be more like UNIX. Windows, yes, but it's not Python's job to turn Windows into a halfhearted UNIX ;-P Besides, that would only alienate the Windows users with Uni(x)fobia. Unix-unix-unix-ly y'rs, -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4