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

pyproject.toml: Move project metadata here from setup.py #110

Merged
merged 1 commit into from Jan 25, 2024

Conversation

mkoeppe
Copy link
Contributor

@mkoeppe mkoeppe commented Jan 25, 2024

That's preparation for but independent of the decision on the build system to use (#52).

@oscarbenjamin oscarbenjamin merged commit 99b0696 into flintlib:master Jan 25, 2024
22 checks passed
@oscarbenjamin
Copy link
Collaborator

Thanks

@oscarbenjamin
Copy link
Collaborator

To be clear I think the decision about a build system is not difficult. I would just use meson but I'm happy to consider alternatives if others would prefer something else. I haven't see any strong opinions about it.

The hold up on switching to meson is just finding the time. I don't know meson that well so it would take me a little while to work out exactly how to do it.

The primary motivation for switching away from setuptools is really just that it doesn't manage building the dependencies like flint. A first step to moving to meson would just be to have a meson configuration that could do the equivalent of bin/build_dependencies_unix.sh which makes a local development build of GMP, MPFR and Flint. That part is already not managed by setuptools anyway.

The main constraint is just that whatever system is used needs to work somehow on Windows.

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.

None yet

2 participants