Menu
I have a "standard" python package layout like this:
However, when I execute setup.py it decides to create the directory src/moduleA.egg-info.
The question is, do I need to worry about the contents of this directory and check it in with the rest of my code, or should I just rely on setuptools/distribute to regenerate it? It seems that all the information in the .egg-info directory comes from the config in setup.py anyway.
228
egg-info format: a file or directory placed adjacent to the project's code and resources, that directly contains the project's metadata.
egg file is a distribution format for Python packages. It's just an alternative to a source code distribution or Windows exe . But note that for pure Python , the . egg file is completely cross-platform.
setuptools allows you to install a package without copying any files to your interpreter directory (e.g. the site-packages directory). This allows you to modify your source code and have the changes take effect without you having to rebuild and reinstall.
Use PyInstaller, py2exe, Nuitka, or another bundling solution. The most convenient way to deliver a Python application to a user is to provide them with an executable—either a single file or a directory with an easily identified executable somewhere in it.
The automatically generated bits don't need to be checked in, unless you're actually extending setuptools itself as part of your build process.
However, if you're putting files of your own in .egg-info (like i18n resources for EggTranslations), then those should definitely be checked in, since setuptools obviously isn't going to be able to regenerate them for you. ;-)
107
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
