-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Remove __init__.py files for subpackages designated to be namespace packages #33011
Comments
Last 10 new commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Work Issues: broken with "configure --enable-editable" (gitpod) |
Changed work issues from broken with "configure --enable-editable" (gitpod) to none |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:65
Replying to @kwankyu:
setuptools 63.1.0 will eliminate them - https://setuptools.pypa.io/en/latest/history.html#v63-1-0 |
comment:66
Replying to @mkoeppe:
Nice! Those |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed dependencies from #28925 to none |
comment:69
I get
There is no Do I need to |
comment:70
Hm, I guess the |
comment:71
|
comment:72
Replying to @mkoeppe:
Yes. it's there. |
comment:73
Replying to @mkoeppe:
I deleted the directory |
comment:75
Replying to @kwankyu:
How about adding a comment like
to guide people what to do to resolve the failure? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:77
I think I found a proper solution for this |
comment:78
Replying to @mkoeppe:
Yes. It looks good. I have some questions. The file Is the complication of removing |
comment:79
Replying to @kwankyu:
I am asking this even though I do not understand the complication (I tried to). |
comment:80
Replying to @kwankyu:
That's right.
Yes, I've opened #34187 for it |
This comment has been minimized.
This comment has been minimized.
comment:81
I think sage is now ready to get this in. |
Reviewer: Kwankyu Lee |
comment:82
Thank you! |
Changed branch from u/mkoeppe/remove___init___py_files_for_packages_designated_to_be_namespace_packages to |
This ticket changes the following packages to namespace packages (by removing
__init__.py
):sage.matrix
(this allows the new distributionsage-meataxe
introduced in Modularization of sagelib: Break out a separate package sagemath-meataxe #30151 to add the modulesage.matrix.matrix_gfpn_dense
) to the package)sage.libs
(for.meataxe
- Modularization of sagelib: Break out a separate package sagemath-meataxe #30151,.sirocco
,.coexter3
,.fes
)sage.interfaces
(for.primecount
)sage.graphs
(for.bliss
,.mcqd
)sage.graphs.graph_decompositions
(for.tdlib
->sage-tdlib
, Modularization of sagelib: Create package sage-tdlib #29864.)sage.numerical
,sage.numerical.backends
. (This is preparation for later work, in sage_setup: Modify clean_stale_files to support out-of-tree namespace packages #30152.)A complication lies in the behavior of the Python import machinery:
setup.py
puts the source path in front ofsetup.py
becausesage_setup
usessage.env
andis_package_or_sage_namespace_package_dir
(#33033).But when an old version of
sage
that is an ordinary package is installed already, the source will not shadow it.To avoid this complication, in this ticket we do not yet remove
src/sage/__init__.py
. That is done in #34187.CC: @tobiasdiez @kwankyu
Component: refactoring
Author: Matthias Koeppe
Branch/Commit:
39aa2f1
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/33011
The text was updated successfully, but these errors were encountered: