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

[Feature]: Allow disabling of TypeMap caching #2045

Open
3 tasks done
rly opened this issue Feb 27, 2025 · 0 comments · May be fixed by #2057
Open
3 tasks done

[Feature]: Allow disabling of TypeMap caching #2045

rly opened this issue Feb 27, 2025 · 0 comments · May be fixed by #2057
Assignees
Labels
category: enhancement improvements of code or code behavior priority: medium non-critical problem and/or affecting only a small set of NWB users
Milestone

Comments

@rly
Copy link
Contributor

rly commented Feb 27, 2025

What would you like to see added to PyNWB?

When a user or developer imports PyNWB for the first time, the type map is loaded and automatically cached in a pickle file in the package in order to speed up load times for future imports. However, this is problematic for developers who are modifying the schema and not seeing those changes reflected because the type map has been loaded from the cache instead of being generated anew. It is very confusing. I would like to be able to turn off loading the type map from cache, perhaps through setting an environment variable after I clone PyNWB onto my laptop.

@mavaylon1 and I looked into other options, such as disabling the type map cache when installing in editable mode, but those did not seem to be foolproof across all various use cases (running tests not in editable mode, users installing from source), so we thought that explicitly setting an environment variable and documenting that in the developer instructions would be the most straightforward.

Is your feature request related to a problem?

No response

What solution would you like?

^

Do you have any interest in helping implement the feature?

Yes.

Code of Conduct

@rly rly added category: enhancement improvements of code or code behavior priority: medium non-critical problem and/or affecting only a small set of NWB users labels Feb 27, 2025
@rly rly added this to the 3.1.0 milestone Feb 27, 2025
@stephprince stephprince linked a pull request Mar 12, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: enhancement improvements of code or code behavior priority: medium non-critical problem and/or affecting only a small set of NWB users
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants