Skip to content
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

reshuffling code to solve #299 #318

Merged
merged 1 commit into from
Feb 6, 2023
Merged

reshuffling code to solve #299 #318

merged 1 commit into from
Feb 6, 2023

Conversation

CommonClimate
Copy link
Collaborator

Also set verbose=False in time_unit_to_datum_exp_dir( ) to avoid incessant notifications.

 Also set verbose=False in time_unit_to_datum_exp_dir( ) to avoid incessant notifications.
@CommonClimate CommonClimate requested a review from khider February 6, 2023 00:24
Copy link
Member

@khider khider left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the functions something you would like someone to access through pyleo.utils, i.e, should they be in the APIs?

@CommonClimate
Copy link
Collaborator Author

I don't think most users will want them in APIs, and in any case it should be tsbase, not tsutils... Marco chose not to export those at the API level, but I am not sure what the pros&cons would be. I think he meant them for internal use only.

@CommonClimate CommonClimate merged commit a37e4a6 into Development Feb 6, 2023
@CommonClimate CommonClimate deleted the tsbase_rework branch February 21, 2023 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants