Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

biogeme 3.2.14 packages the __pycache__ directories #41

Open
moorepants opened this issue Aug 31, 2024 · 1 comment
Open

biogeme 3.2.14 packages the __pycache__ directories #41

moorepants opened this issue Aug 31, 2024 · 1 comment

Comments

@moorepants
Copy link

If you download the source tarball you can find __pycache__ directories present:

biogeme-3.2.14$ find . -name "__pycache__"
./src/biogeme/tools/__pycache__
./src/biogeme/expressions/__pycache__
./src/biogeme/__pycache__
./src/biogeme/mdcev/__pycache__
./src/biogeme/sampling_of_alternatives/__pycache__
./src/biogeme/data/__pycache__
./src/biogeme/models/__pycache__

These should not be packaged in a source tarball.

They cause warnings such as these:

  /home/conda/feedstock_root/build_artifacts/biogeme_1725082603608/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'biogeme.tools.__pycache__' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'biogeme.tools.__pycache__' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'biogeme.tools.__pycache__' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'biogeme.tools.__pycache__' to be distributed and are
          already explicitly excluding 'biogeme.tools.__pycache__' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!

and could cause errors when installing.

@moorepants
Copy link
Author

I noticed this here: conda-forge/biogeme-feedstock#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant