Hi, thanks for the new release great job. Lot of new features.
I have done some testing with a internal application for Windows 64bit building as service and console application. Changes I have noticed but are not clear from documentation: 1. For the distutils build command some options are now only allowed for the Executable and no longer as general option (ex. "icon") This is no problem but it is also not documented. 2. Scripts or zips can no longer be appended to the executable. As noted in the documentation. Because the script to execute (import) is now searched in the path with the executable name and a postfix appended it is no longer possible to create a executable with a version number like: example-5.1.7.exe and specifying to use the script "example.py". It is ok but should be added to the documentation how the new mechanism works and the limitations. 3. With version < 5.0 the main script was imported/executed with __name__ == "__main__" setup to handle the usual Python if __main__ guard. With version >= 5.0 this is no longer the case. The script is only imported and only top level stuff is executed. Not a big deal, can be solved by simply creating a stub script with the needed lines. But should be documented. 4. Failed pywintypes import. But this was already detected and is fixed in a newer version. Over all I like the new features and simplification. This allows adding more new useful features. Possibly (only ideas): 1. Use requirements.txt to get package dependencies in addition to scanning imports. 2. Option to automatic bundle whole Python standard library to application. Thanks. Regards, Wolfgang ------------------------------------------------------------------------------ _______________________________________________ cx-freeze-users mailing list cx-freeze-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
