-
Notifications
You must be signed in to change notification settings - Fork 230
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
loadPackage fails for hard to determine reason #3308
Comments
I've heard of this complaint from a lot of people, and the answer has always been
I'd be in favor of ditching |
Here's a proposal: Currently we have (in particular, a local copy of a package in the current directory will have a different location, so |
This was the suggestion in #3225, by the way. Any feedback or whether or not you agree with change would be useful. |
Sometimes, calling
loadPackage
can fail, saying it cannot be reloaded.This error occurred in a set of packages I wrote a few years ago. I have boiled it down to its essence:
In
A.m2
, place the codeIn
B.m2
, place the codeNow after creating these files, try the following code.
This last line fails, since the package ''A" has been loaded when "B" is being scanned for its newPackage code (I think), and so has already been loaded. This is very hard to determine, as any installed package could do this and cause the package to simply be loaded already... Using
needsPackage
works fine.Also, the time to install the package "A" seems to take 4-5 seconds on my machine, which seems quite large. (Same with "B").
The text was updated successfully, but these errors were encountered: