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

unload_namespace #1009

Open
5 tasks done
bendichter opened this issue Jul 13, 2019 · 1 comment
Open
5 tasks done

unload_namespace #1009

bendichter opened this issue Jul 13, 2019 · 1 comment
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 topic: validator issues related to validation of files
Milestone

Comments

@bendichter
Copy link
Contributor

2) Feature Request

Right now it is difficult to test the load_namespaces flag in NWBHDF5IO for reading a custom extension. If you create an extension and an API either from get_class or from manually writing a class, this requires you to call load_namespace. Then if you try to use the load_namespaces flag in NWBHDF5IO that namespace will be skipped since it has already been loaded. I propose a new function, unload_namespace, which will remove a namespace from the type map, allowing you to test the read through load_namespaces.

Checklist

  • Have you ensured the feature or change was not already reported ?
  • Have you included a brief and descriptive title?
  • Have you included a clear description of the problem you are trying to solve?
  • Have you included a minimal code snippet that reproduces the issue you are encountering?
  • Have you checked our Contributing document?
@t-b
Copy link
Collaborator

t-b commented Jul 13, 2019

This sounds a bit like a work around for the globals in

# a global namespace catalog
global __NS_CATALOG
global __TYPE_MAP
__NS_CATALOG = NamespaceCatalog(NWBGroupSpec, NWBDatasetSpec, NWBNamespace)

or? Why do we need the globals anyway?

@stephprince stephprince self-assigned this Apr 12, 2024
@stephprince stephprince added category: enhancement improvements of code or code behavior priority: medium non-critical problem and/or affecting only a small set of NWB users topic: validator issues related to validation of files labels Apr 12, 2024
@stephprince stephprince added this to the Next Major Release - 3.0 milestone Apr 12, 2024
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 topic: validator issues related to validation of files
Projects
None yet
Development

No branches or pull requests

3 participants