-
Notifications
You must be signed in to change notification settings - Fork 37
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
Provide better exposure for methods in pysat._files #336
Comments
I have a test branch up in #454. The change is straightforward and works, but rapidly becomes confusing to me due to the existence of the Possible routes:
|
Moving the relevant methods to pysat.utils.files sounds like a good plan to me. |
OK. I'll start mocking up a replacement PR. This will require deprecation warnings. |
Looking over the code, it looks like |
That’s a class method. It has to be defined within the Files class.
|
Closing with merge of #505 |
Is your feature request related to a problem? Please describe.
Users may not be aware of built in file methods that could make their lives easier when adding new instruments.
Describe the solution you'd like
rename pysat._files.py to pysat.files.py
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: