pyinstaller packaging about puresnmp HOT 7 CLOSED

I have no experience with pyinstaller.

Having a version.txt in the project makes it easy to change version numbers as you have only one single location to modify and makes it very easy to read with other external tools during development. If there is no way to fix the pyinstaller packaging without internalising the version number then I don't see an issue with internalising.

If you can, investigate the exact issue with pyinstaller. It sounds to me like it's ignoring MANIFEST.in and/or the include_package_data flag from setup.py.

I would be surprised if pyinstaller would have problems with "package data" as it is a standard feature for Python packages.

from puresnmp.

I recently ran into similar issues with pyinstaller. It really seems that pyinstaller is not respecting the MANIFEST.in file. As a workaround you can use the --add-data option. Like so

pyinstaller --noconsole --add-data "project_name/version.txt" startup.py

Quick question though. Are you using puresnmp in another package of yours for which you would like to compile an Windows executable file?

from puresnmp.

Given that this is not really an issue with puresnmp I will close this.

Thanks @flazzarini for pointing out the solution.

from puresnmp.

Needs to be reviewed.

from puresnmp.

@remdragon I've moved the version info into a python file instead of a text file. Can you try if this works better with pyinstaller?

from puresnmp.

from puresnmp.

Oh, I realised I forgot to upload the latest release-candidate from today to pypi. But in any case, the new release is currently flagged as "prerelease" (using the rc<n> suffix) which pip ignores by default. I want to keep it as RC until you give me green light to flag it as final. You can also see this on the pypi history page

To allow pip to include the pre-release, you can add the --pre flag.

Or use the following as dependency: puresnmp >= 1.3.0rc3

from puresnmp.