-
Notifications
You must be signed in to change notification settings - Fork 10
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
desiInstall creates incorrect module file for QuasarNP #172
Comments
@sbailey, is |
@sbailey, never mind, I know exactly what is happening. This is a corner case we've never encountered before. We have successfully installed software products that do not have a The fastest possible way to fix this would be to rename the GitHub repo |
I dislike capitals in github product names, especially when that causes the python package to have a different case-sensitive name from its github product name, but I will defer to @dylanagreen and @dkirkby as the maintainers of that package for how strongly they feel about the capitalization, which I suspect they chose to mimic QuasarNET from which QuasarNP is adapted. Either way, @weaverba137 I'll submit a PR with an additional check for this case. |
OK, but keep in mind, that mixed-case to lower-case is not the only possible combination. So you have to check for all possible combinations of upper and lower case, and yet still retain the correct information about the name of the package and the name of the directory. And, in principle, the alternate-case package name could be inside a Still, if you're able to add unit tests for all these possible cases (in both senses of the word), then we can be reasonably confident going forward. Finally, the check for these directories happens in |
QuasarNP is a semi-external package hosted in desihub. It doesn't have a boilerplate etc/quasarnp.module file, but it also doesn't require anything custom so I was expecting the desiInstall default module file to work. desiInstall does correctly identify the "py" install and pip installs QuasarNP, but the resulting module file doesn't add $PRODUCT_DIR/lib/python3.8/site-packages to $PYTHONPATH.
The text was updated successfully, but these errors were encountered: