EnvGap
PyPI licence tags
envgap__snowballstem__snowball-100
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
3d86a3318912ae7c7701f20e513f4eee2c65e0c5- Manifest
python/setup.py- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
snowballstem/snowball #100 · read the original issue
@mitya57 This was held for moderation by the mailing list, but it didn't seem relevant for most subscribers (and I'm not sure if you're even subscribed to the list) so putting it in an issue here instead: >Hello! > >You have recently released a new version of snowballstemmer. Thanks! It will >probably make a lot of people happy. There is a tiny issue with your >package on PyPI though: it is a bit difficult to guess the exact >license you use. > > >It is very clear that you use one of the BSD licenses. PyPI allows you >to use the following classifier: > > License :: OSI Approved :: BSD License > >But it is not very precise. You can also use the "license" field in >setuptools, but there is no "fixed" format, so you could write "BSD2", >"BSD-2", "BSD-2-Clause", etc. This makes it hard for automated tools >to properly guess which BSD license you are using. > >May I suggest using the aforementioned classifier *and* an SPDX >identifier (https://spdx.org/licenses/) in the "license" field? > > >Thanks, >Cyril Roelandt > >(This email was automatically generated, but you can answer it! A real >human being will read your answer.) (If you think it makes more sense to list your address as maintainer for PyPI rather than the mailing list, please do).
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]