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

PEP 517 requires causes: error: aborting due to unexpected upstream changes #185

Open
couling opened this issue Feb 8, 2022 · 0 comments

Comments

@couling
Copy link

couling commented Feb 8, 2022

I'm having problems with py2dsc not interacting well with PEP 517 requires see here.

For example if using setuptools_scm to control version numbering the pyproject.toml might look like this:

[build-system]
requires = ["setuptools>=45", "wheel", "setuptools_scm>=6.2"]

[tool.setuptools_scm]

And for legacy setup.py might look like this:

from setuptools import setup

setup(setup_requires=['setuptools_scm'])

This means that building or installing the package will install a third party package only for use by setup.py.

As I understand it, setup.py is not included in in the final .deb and so the third party package is also not needed. But because py2dsc runs setup.py it then errors out with:

dpkg-source: error: aborting due to unexpected upstream changes, see ...

And it lists .eggs/setuptools_scm and friends as the unexpected changes.


There's a workaround by:

pip install setuptools_scm

Prior to calling py2dsc but it would be nice if .eggs there was an inline solution.

@couling couling changed the title PEP 517 PEP 517 requires causes: error: aborting due to unexpected upstream changes Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant