Repository navigation
PyPi tarball is missing files #141
Description
From PyPi:
python-slugify-8.0.1/
python-slugify-8.0.1/CHANGELOG.md
python-slugify-8.0.1/LICENSE
python-slugify-8.0.1/MANIFEST.in
python-slugify-8.0.1/PKG-INFO
python-slugify-8.0.1/README.md
python-slugify-8.0.1/python_slugify.egg-info/
python-slugify-8.0.1/python_slugify.egg-info/PKG-INFO
python-slugify-8.0.1/python_slugify.egg-info/SOURCES.txt
python-slugify-8.0.1/python_slugify.egg-info/dependency_links.txt
python-slugify-8.0.1/python_slugify.egg-info/entry_points.txt
python-slugify-8.0.1/python_slugify.egg-info/not-zip-safe
python-slugify-8.0.1/python_slugify.egg-info/requires.txt
python-slugify-8.0.1/python_slugify.egg-info/top_level.txt
python-slugify-8.0.1/setup.cfg
python-slugify-8.0.1/setup.py
python-slugify-8.0.1/slugify/
python-slugify-8.0.1/slugify/__init__.py
python-slugify-8.0.1/slugify/__main__.py
python-slugify-8.0.1/slugify/__version__.py
python-slugify-8.0.1/slugify/slugify.py
python-slugify-8.0.1/slugify/special.py
From github tarball:
python-slugify-8.0.1/
python-slugify-8.0.1/.github/
python-slugify-8.0.1/.github/workflows/
python-slugify-8.0.1/.github/workflows/ci.yml
python-slugify-8.0.1/.github/workflows/dev.yml
python-slugify-8.0.1/.github/workflows/main.yml
python-slugify-8.0.1/.gitignore
python-slugify-8.0.1/.vscode/
python-slugify-8.0.1/.vscode/settings.json
python-slugify-8.0.1/CHANGELOG.md
python-slugify-8.0.1/LICENSE
python-slugify-8.0.1/MANIFEST.in
python-slugify-8.0.1/README.md
python-slugify-8.0.1/dev.requirements.txt
python-slugify-8.0.1/format.sh
python-slugify-8.0.1/setup.py
python-slugify-8.0.1/slugify/
python-slugify-8.0.1/slugify/__init__.py
python-slugify-8.0.1/slugify/__main__.py
python-slugify-8.0.1/slugify/__version__.py
python-slugify-8.0.1/slugify/slugify.py
python-slugify-8.0.1/slugify/special.py
python-slugify-8.0.1/test.py
The .github/* files obviously are not needed, but test.py is missing, so that tests can't be run if one downloads the PyPi distribution.
Activity
un33k commentedon Jan 16, 2024
@nieder I've never used PyPi myself. Community members have added that to the builds. Unless community members raise a PR, there is no plane to further investigate this.
nieder commentedon Jan 19, 2024
Interesting. I knew wheels could be community built on PyPi, but not the tarballs. Anyway, I'll keep using the github tarball.
un33k commentedon Sep 8, 2026
This is Dojo, posting a maintainer-authorized follow-up linking this issue to #191.
Source archive contents are explicitly included and checked for newly built artifacts. Existing published PyPI archives are not repaired or replaced.
The default algorithm remains legacy; improved output rules are opt-in. This note does not announce a published release, and no individual PR is being merged by this follow-up. Thank you for the contribution and discussion.
🚀 Generated with Dojo ⛩️