-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
Needs DiscussionIssues where the implementation still needs to be discussed.Issues where the implementation still needs to be discussed.Needs InvestigationIssues which are likely in scope but need investigation to figure out the causeIssues which are likely in scope but need investigation to figure out the causebughelp wanted
Description
setuptools version
setuptools==66.0.0
Python version
python 3.8
OS
macOS
Additional environment information
No response
Description
I am building a wheel for a python package using setuptools and it seems that the naming of my wheel file is not respecting the PEP 491 convention.
For external reasons, I need to name my package with the structure {namespace}.{package-name}. If I follow the convention, I would expect that my wheel file is named: namespace_package_name-0.1.0-py2.py3-none-any.whl.
However, I get this name for my wheel: namespace.package_name-0.1.0-py2.py3-none-any.whl, which is not respecting the convention.
Expected behavior
I expect the "." in the package name to be replaced with a "_" in the wheel name.
How to Reproduce
- create a hello_world package structure:
hello_world |- my_package | |- __init__.py | |- hello_world.py |- pyproject.toml |- setup.cfg - in
setup.cfg, write:[metadata] name = namespace.my-package version = 0.1.0 [options] zip_safe = False include_package_data = True packages = find: - in
project.toml, write:[build-system] requires = ["setuptools==66.0.0", "wheel"] build-backend = "setuptools.build_meta" - run
pipx run buildat the root of your hello_world package - inspect the
distdirectory which was created
Output
in the dist folder, you find:
namespace.my_package-0.1.0-py3-none-any.whl
konstin and jamesbraza
Metadata
Metadata
Assignees
Labels
Needs DiscussionIssues where the implementation still needs to be discussed.Issues where the implementation still needs to be discussed.Needs InvestigationIssues which are likely in scope but need investigation to figure out the causeIssues which are likely in scope but need investigation to figure out the causebughelp wanted