With the old setuptools based way of freezing executables, running the setup.py similar to the one below resulted in different version and description for each of the frozen binaries.
from setuptools import setup
import py2exe
setup(
console=[
{"script": "bin1.py", "description": "Binary 1", "version": "22.1.6"},
{"script": "bin2.py", "description": "Binary 2", "version": "2.3.4"}
]
)
This example is obviously artificial - we were using similar pattern when freezing NVDA, at least some parts of version info is different for each binaries we're freezing. While with the new freeze API it is possible to specify version_info for all of the frozen binaries, it seems impossible to make it different for each one.
@albertosottile Would you be able to tell if the change was intentional, and if it was what was the reasoning behind it? Assuming this was not intended would you be open to a PR reintroducing the behavior. While this is not a show stopper for NVDA it would be nice not to change version info for our binaries unnecessarily. In terms of design I'd imagine adding additional version_info dictionary to each windows and console target should offer the needed flexibility.
With the old setuptools based way of freezing executables, running the
setup.pysimilar to the one below resulted in different version and description for each of the frozen binaries.This example is obviously artificial - we were using similar pattern when freezing NVDA, at least some parts of version info is different for each binaries we're freezing. While with the new freeze API it is possible to specify
version_infofor all of the frozen binaries, it seems impossible to make it different for each one.@albertosottile Would you be able to tell if the change was intentional, and if it was what was the reasoning behind it? Assuming this was not intended would you be open to a PR reintroducing the behavior. While this is not a show stopper for NVDA it would be nice not to change version info for our binaries unnecessarily. In terms of design I'd imagine adding additional
version_infodictionary to eachwindowsandconsoletarget should offer the needed flexibility.