$SAGE_ROOT/src/MANIFEST.in

[ph h]

Dear All,

How do these 'include' statements in 'MANIFEST.in'  work?

What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'?

Is there a corresponding 'MANIFEST' generated from this  'MANIFEST.in' ? 

Thank you for your help.

Regards,

phiho

<MANIFEST.in>

global-include *.c *.cc *.cpp *.h *.hh *.hpp *.inc *.py *.pyx *.pxd *.pxi *.rst *.txt *.tex

include MANIFEST.in
include pyproject.toml

prune .tox
graft   sage/libs/gap/test
prune sage/ext/interpreters   # In particular, __init__.py must not be present in the distribution; or sage_setup.autogen.interpreters.rebuild will not generate the code
prune sage_setup

</MANIFEST.in>

[Matthias Koeppe]

See https://packaging.python.org/en/latest/guides/using-manifest-in/

This is not specific to Sage.

[ph h]

Hi,

> > What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'?

> See https://packaging.python.org/en/latest/guides/using-manifest-in/

> This is not specific to Sage.

This is very interesting.

Thanks so much.

phiho

--
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 sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2d5890f5-9033-4dab-a668-81c19db0839an%40googlegroups.com.