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

Support for packages without setup.py #200

Open
glemignot opened this issue Jul 5, 2024 · 6 comments
Open

Support for packages without setup.py #200

glemignot opened this issue Jul 5, 2024 · 6 comments
Labels

Comments

@glemignot
Copy link

More and more Python packages are using pyproject.toml instead of setup.py. Is there any plan to add support for those to stdeb ? Or is there another project aiming to convert those into Debian packages ?

@nuclearsandwich
Copy link
Collaborator

The python packaging ecosystem seems to be in a state of heavy flux and I don't co-maintain any projects that are completely without a setup.py.

While that remains the case, support for such functionality would need to be driven by contributors.
Is there a specific project that you'd use stdeb with but cannot because the project lacks setup.py?

@WilliamDEdwards
Copy link
Contributor

Is there a specific project that you'd use stdeb with but cannot because the project lacks setup.py?

Pika, Typer.

@nuclearsandwich
Copy link
Collaborator

Thanks. Both pika and typer are available in Debian unstable, which means that packaging support for packages without setup.py exists upstream.

A brief spy of the debian/rules for typer also doesn't have anything too fancy.
It could be that simplifying stdeb and switching it to use pybuild will help these to Just Work™️.

The amount of time that I have to dedicate to this is extremely uncertain, if you're interested in contributing these changes, I'd suggest subscribing to #198 as I imagine doing so will be much easier after that is in.

@WilliamDEdwards
Copy link
Contributor

I don’t need to build them anymore, indeed. But up until Buster IIRC, the upstream repo’s versions were extremely outdated. It was fine at the time because the projects still had a setup.py, but other users might need patched versions or similar.

@glemignot
Copy link
Author

Recently we had a need for https://pypi.org/project/django-pictures/, but we found another solution. More generally, I suspect there will be more and more Python packages not having a setup.py in the future, so this feature would likely get more useful as time goes, but I understand lack of time and manpower (I'm having the same issue...).

@WilliamDEdwards
Copy link
Contributor

The amount of time that I have to dedicate to this is extremely uncertain, if you're interested in contributing these changes, I'd suggest subscribing to #198 as I imagine doing so will be much easier after that is in.

I'm not interested in contributing these changes due to a lack of time. However, I would be more than happy to support the project financially to get this done. Perhaps you or @astraw want to consider bounties?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants