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

Migrate from setuptools/distutils to meson #23

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

eylles
Copy link
Contributor

@eylles eylles commented Jun 18, 2024

initial work to fully migrate towards meson, huge thanks to karna for not just sending the patch but testing that it builds under debian testing.

as outlined on the patch comment there is still work to do.

Replaces usage of distutils to build c extension with
meson/meson-python. This requires replacing the `setup.py` file with
a `pyproject.toml` file, which makes it harder to infer project
properties from the python source.
@eylles
Copy link
Contributor Author

eylles commented Jun 18, 2024

yes this is a work towards #9 #13 #14

i guess @ionenwks @pirate486743186 and @eli-schwartz will be happy to know this is finally getting worked on.

@eli-schwartz
Copy link

Nice. The meson.build part looks mostly like the one minimally tested and suggested at #14 (comment) but the summary() usage is new.

IIRC meson already prints settings that were changed from the defaults, although py_install_dir isn't a setting to change so still possibly good to see. I'm not sure whether the other settings (get_option usages) even matter for ueberzug's use case? In theory you could just elide printing those. :)

@eylles
Copy link
Contributor Author

eylles commented Jun 18, 2024

@eli-schwartz

I'm not sure whether the other settings (get_option usages) even matter for ueberzug's use case?

i thought so at first, but since the long term intention is to try and have some feature parity with U++ they could come in handy in the future.

also there is another rather pressing problem, which is that the distribution name ueberzug is blocked on pypi #20 so it is not possible to upload a new ueberzug there and the PEP 541 request doesn't seem like it will have a quick resolution, so either as a project we give up on pypi or upload under a different name, of ever suggestion i like ueberzug-community the most, but that causes a "small" issue with the name of the wheel changing since twine infers the pypi dist name from the wheel, so that would create a burden either with the distro maintainers to change the name on the pyproject.toml with a patch OR that the gh action to build and upload the pypi dist will need to change the name var... and neither seems "correct" if you ask me.

@eylles
Copy link
Contributor Author

eylles commented Jun 24, 2024

also there is another rather pressing problem, which is that the distribution name ueberzug is blocked on pypi #20 so it is not possible to upload a new ueberzug there and the PEP 541 request doesn't seem like it will have a quick resolution, so either as a project we give up on pypi or upload under a different name, of ever suggestion i like ueberzug-community the most, but that causes a "small" issue with the name of the wheel changing since twine infers the pypi dist name from the wheel, so that would create a burden either with the distro maintainers to change the name on the pyproject.toml with a patch OR that the gh action to build and upload the pypi dist will need to change the name var... and neither seems "correct" if you ask me.

will figure this one later, will test some stuff and hopefully merge this today.

@eylles
Copy link
Contributor Author

eylles commented Jun 26, 2024

will test some stuff and hopefully merge this today.

hopefully merge this today.

merge this today.

lol, lmao even.

@eylles eylles merged commit e92e5f6 into ueber-devel:master Jun 26, 2024
@eli-schwartz
Copy link

You don't get a high score until you've delayed merging your own PR by a couple of years. :P

(Been there, done that, hid the t-shirt in the back of the drawer.)

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

Successfully merging this pull request may close these issues.

2 participants