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

Using License EPL-2.0 results in errors when publishing to pypi.org #9803

Closed
netomi opened this issue Oct 27, 2024 · 0 comments · Fixed by python-poetry/poetry-core#784
Closed
Labels
kind/bug Something isn't working as expected status/triage This issue needs to be triaged

Comments

@netomi
Copy link

netomi commented Oct 27, 2024

Description

When specifyingEPL-2.0 as license in the pyproject.toml file, the following classifier is added automatically:

License :: OSI Approved :: Eclipse Public License 2.0

however, when publishing the wheel to pypi, the publishing fails with an error as the classifier is unknown.

Looking at the currently listed classifiers, you see that the name for EPL licenses slightly changed:

image

Workarounds

There is no acceptable workaround right now, as there seems to be no way to disable or skip the automatic generation of classifiers from the license.

A workaround is to specify a license like that:

license       = "Eclipse Public License 2.0 (EPL-2.0)"

however this leads to an classifier added automatically like that:

Classifier: License :: Other/Proprietary License

which is not really what you want.

Poetry Installation Method

pipx

Operating System

Ubuntu 22.04

Poetry Version

1.8.4

Poetry Configuration

cache-dir = "/home/tn/.cache/pypoetry"
experimental.system-git-client = false
installer.max-workers = null
installer.modern-installation = true
installer.no-binary = null
installer.parallel = true
keyring.enabled = true
solver.lazy-wheel = true
virtualenvs.create = true
virtualenvs.in-project = true
virtualenvs.options.always-copy = false
virtualenvs.options.no-pip = false
virtualenvs.options.no-setuptools = false
virtualenvs.options.system-site-packages = false
virtualenvs.path = "{cache-dir}/virtualenvs"  # /home/tn/.cache/pypoetry/virtualenvs
virtualenvs.prefer-active-python = false
virtualenvs.prompt = "{project_name}-py{python_version}"
warnings.export = true

Python Sysconfig

No response

Example pyproject.toml

[tool.poetry]
name          = "otterdog"
version       = "0.8.0-dev"
description   = "Tool to manage GitHub organizations and their repositories."
authors       = ["Thomas Neidhart <[email protected]>"]
readme        = "README.md"
license       = "EPL-2.0"

Poetry Runtime Logs

N/A
@netomi netomi added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Oct 27, 2024
@netomi netomi changed the title Using License EPL-1.0 or EPL-2.0 results in errors when publishing to pypi.org Using License EPL-2.0 results in errors when publishing to pypi.org Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working as expected status/triage This issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant