From: Friedrich R. <fri...@gm...> - 2009-07-07 18:57:30
|
Hello! It would be great to make Pmw working with modern :-) py2exe and py2app. At the moment, one needs quite many tweaks to overcome the restrictions of the bundling of the packages into library.zip (py2exe) and to get Pmw.def included (py2exe). To use Pmw with this, one has to disable the library.zip (py2exe) or has to write a recipe (py2app). Most users are not able to do this, I'm afraid. It blows up the archive a lot (py2exe) resp. a bit (py2app). I think a way to overcome the path-related stuff and to keep the auto-search function would be to either replace the whole package on installation or to replace only __init__.py on installation. For the second case, it would be possible to do something like versions = [(0,1,2),(0,1,3)] for version in versions: try: ...import code... except: pass An update would replace only the line "versions = ..." But when we are going to replace something on installation it would make more sense for me to simply replace the __init__.py by something straightforward and non-magic like from Pmw_1_2 import * This is easier to understand, easier to fix, less error prone and easier to configure even by Python newbies. The Pmw.def could be replaced by a simple Config.py defining the needed constants. What do you think about this? When I get some time, I will try to dive into Pmw to get this working. I think Pmw is quite dead because it's in functionality quite mature. It's a great concept of hull_border='sunken' etc. and I think most users simply use it and have no need to contribute any patches, except at least two people on the world who want to freeze their Python app ... Wishing you the best, Friedrich |