-
Notifications
You must be signed in to change notification settings - Fork 56
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
Refactor #248
Refactor #248
Conversation
We should merge this after #241, there are some conflicts between the two. Just couple of comments from my side concerning packaging: I would strongly recommend to keep user code separate from the pygama codebase, so I would not move those JSON files from About third-party, non-python code like Eigen: I think this should also be placed elsewhere, maybe in a folder at the repo root dedicated to third party projects. We should think about it also install-wise. I'm also usually more in favor of directly mirroring the code in our repository, instead of using Git submodules, which are sometimes painful to handle. Let's discuss this too next time we meet! |
Thanks for the comments, Luigi. I've:
As for the remaining merge conflicts, once we get #241 in, I can revisit the merge conflicts. |
Co-authored-by: Luigi Pertoldi <gipert@pm.me>
@iguinn we are ready for you to revisit this |
with importlibs.resources.path("pygama.metadata", "file.json") as p: ...