aboutcode-org / aboutcode-org/python-publicsuffix2

tests missing in sdist/ incoherent tagging vs tarball naming

未关闭
#12 6 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
30
派生
16
PR 合并指标
30 天内没有已合并 PR

描述

Hi! I'm packaging python-publisuffx2 for Arch Linux and would like to be able to run tests from the sdist tarball on pypi.
Although the test files should be included (according to MANIFEST.in), they are not.

As a test I've checked out the current latest version (release-2.2019-12-21) and ran `python setup.py sdist` myself. The files are included in the created sdist tarball, which makes me wonder how the sdists for pypi.org were created.

It would be great, if the sdists included the tests, as currently I have to use the github tarballs to be able to run the tests.

This leads me to the second topic: The tag naming and resulting tarballs are incoherent and lead to more complicated string substitutions to track upstream and/or use the github source tarball vs. using pypi's sdist tarball: `release-2.2019-12-21` -> `publicsuffix2-2.20191221.tar.gz`
I understand, that the tagging scheme so far follows an ISO standard for the date, but it would be more coherent to strip the hyphens to be in line with the resulting tarball/wheel: e.g. `release-2.20191221` -> `publicsuffix2-2.20191221.tar.gz`

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。