-
Notifications
You must be signed in to change notification settings - Fork 12
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
Reorganize project structure #49
Comments
Done. The new repositories are: https://github.com/xnd-project/xnd |
The issue is finished, but it will be left open and pinned so people can see what is going on. |
It would be good to unpin |
Ideally the proper history of all libraries should be restored, but merging all three turned out to be quite difficult. If this setup proves successful, it can be done later. |
@skrah, it nice to hear from you again! Yes, let me try to restore the privileges. Could you contact me via private email as I think I don't have your contacts? |
After the deprecation of distutils the separate libraries are hard to maintain. To facilitate maintenance and development, the following changes will be made:
Repository renamings
ndtypes
==>libndtypes
xnd
==>libxnd
gumath
==>libgumath
These are of course easily reversible if the new structure does not work out.
New combined repository
The new combined repository will be named
xnd
and will contain all libraries and Python modules. The Python modules have a dual function: They are built for running the library tests but they are also the authoritative source for the Python packages.Build system
In order to maximize independence from the Python packaging machinery,
xnd
will be entirely built byCMake
.CMake
has excellent support for building Python C-extensions without relying on any third party packages.The Python modules built by
CMake
are of course directly usable for testing and development, thereby making support for editable installs unnecessary.Python packages
A separate
xndpy
repository will contain the necessary code for building packages. The actual build will utilizeCMake
, the packaging routines will be handled by a custom backend,flit
andpyproject.toml
. Developers will never need this, see above.The text was updated successfully, but these errors were encountered: