Yes, I do see sagemath-10.8b5.dist-info which I guess must be the metadata for sagelib.
- Marc On Saturday, October 4, 2025 at 1:28:14 AM UTC-5 [email protected] wrote: > Thanks for the clarification. However, sage-the-distro does use pip to > install the sagemath (not sage!) package, see build/pkgs/sagelib/ > spkg-install.in - so it is a 'proper' pip + python package. > > On Thursday, October 2, 2025 at 9:27:22 PM UTC+8 [email protected] wrote: > >> Mostly I just meant that things are in transition. I should have said >> that there is no *pip* package. >> >> When I look in sage/lib/python3.13/lib/site-packages I see: >> >> sage >> sage_conf-10.8b5.dist-info >> sage_conf.py >> sage_docbuild >> sage_docbuild-10.8b5.dist-info >> sage_numerical_backends_coin >> sage_numerical_backends_coin-10.4.dist-info >> sage_setup >> sage_setup-10.8b5.dist-info >> >> So it looks to me like sage_conf, sage_docbuild, >> sage_numerical_backends_coin and sage_setup all have metadata but sage does >> not. There is no sage-10.8.dist-info. I agree there is a sage package, >> meaning there is a directory named "sage" containing a file named >> "__init__.py", but that package is different from most of the other >> packages (all except omp, I think) which have dist-info directories >> containing metadata. I think that just means that while sage is >> technically a python package, it is not a package installed by pip, and as >> such it does not have metadata, so it does not advertise its entry points >> in the way that pip-installed packages do. >> >> - Marc >> >> On Thu, Oct 2, 2025 at 1:53 AM '[email protected]' via sage-devel < >> [email protected]> wrote: >> >>> >>> They are not exactly entry points, since they are not advertised in the >>> package metadata since there is no package metadata since there is no >>> package (yet). >>> >>> >>> I don't understand what you mean with this sentence. There is a sagemath >>> package, defined in the pyproject.toml file in the root, whose metadata >>> (project.scripts) declares the entry point "sage" with implementation in >>> the Python module "sage.cli". This is the standard way how Python projects >>> register scripts/entry points, i.e. create executables in venv/bin upon >>> installation. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "sage-devel" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/sage-devel/t5Nxu61MhMI/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion visit >>> https://groups.google.com/d/msgid/sage-devel/d94c02a7-93ec-4bb7-a504-df25b931cb35n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/sage-devel/d94c02a7-93ec-4bb7-a504-df25b931cb35n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/1ee81e9a-a744-4bd9-980b-3cb221afa260n%40googlegroups.com.
