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.

classification
Title: mkcwproject: custom __initialize routine
Type: enhancement Stage:
Components: macOS Versions:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: jvr Nosy List: jackjansen, jvr
Priority: low Keywords:

Created on 2001-12-13 14:23 by jvr, last changed 2022-04-10 16:04 by admin. This issue is now closed.

Messages (4)
msg8131 - (view) Author: Just van Rossum (jvr) * (Python triager) Date: 2001-12-13 14:23
Both for _Tkinter and CoreGraphics it is neccesary to
specify a custom fragment initializer. It would be nice
if this were doable with mkcwproject, as it would reduce
the number of CW project file under CVS by 4...
msg8132 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2002-05-23 22:37
Logged In: YES 
user_id=45365

genpluginprojects has been modified to allow an optional initialize=xxx keyword argument (and its mkcwproject foundation too). The only thing I've tested is that it doesn't have any adverse effects on the existing projects that are built. Assigning it back to you so you can try to generate the CG project with it and remove the hand-built CG project file. If that all works assign it back to me and I'll do the same for Tkinter.
msg8133 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-02-24 16:42
Logged In: YES 
user_id=45365

Just, what do you think about closing this with a "won't fix"?
msg8134 - (view) Author: Just van Rossum (jvr) * (Python triager) Date: 2003-02-24 18:44
Logged In: YES 
user_id=92689

Good idea, it's not like CW+CFM has a great future for Python anyway...
History
Date User Action Args
2022-04-10 16:04:45adminsetgithub: 35733
2001-12-13 14:23:22jvrcreate