DOC: editable: clarify file guarantees with non-Python files #786
Conversation
| available in a regular installation. However, depending on the file | ||
| and directory organization in your project, it might also expose files | ||
| that would not be normally available. | ||
| that would not be normally available. Furthermore, some files written in | ||
| other languages to Python may not be available. |
There was a problem hiding this comment.
Uh? This is actually false. Where did you get the impression that only Python files are exposed?
There was a problem hiding this comment.
Where did you get the impression that only Python files are exposed?
I didn't get the impression that only Python files are exposed — that isn't what this says!
I did get the impression that some files in other languages may not be available: see numpy/numpy#29490.
There was a problem hiding this comment.
All installed files are available, if you look them up with the proper Python API.
I really don't understand what you are trying to communicate with these edits. Most likely I don't understand what you mean with "Python file". After all, meson-python is mostly used to build packages that contain Python modules written in other languages that Python, therefore, if these sometimes were to go missing, it would be a major issue.
I guess that you are trying to access installed files by their (expected) filesystem location rather than through the Python API. A few lines above the text you are amending we have this sentence:
This will install a stub in the Python site packages directory that loads the package content from the sources and build directory.
I thought that this should be indication enough that the installed files do not exist in the filesystem at the location where they would be in an normal isntallation. But I have the impression that this is not picked up by most readers. What we really need is a "Accessing data files" in the editable install documentation that spells this out.
closes numpy/numpy#29490 @rgommers