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

Schema paths with only package name won't load #115

Open
StokesMIDE opened this issue Jun 10, 2022 · 0 comments
Open

Schema paths with only package name won't load #115

StokesMIDE opened this issue Jun 10, 2022 · 0 comments
Labels
development Development issues: package deployment, project organization, etc. enhancement New feature or request Schema Related to the EBML schemata

Comments

@StokesMIDE
Copy link
Member

In SCHEMA_PATH, package-relative paths containing only the package name don't work; even though idelib.schemata is a valid, importable submodule, "{idelib.schemata}" doesn't work. It will work if followed by a slash ("{idelib.schemata}/"), however. This works, but it would be nice if the package names could be kept 'pure', as opposed to a combination of a module name and a filesystem path.

The simplest fix would be to have core._expandSchemaPath() include a slash if the path ends with a brace.

@StokesMIDE StokesMIDE added enhancement New feature or request Schema Related to the EBML schemata development Development issues: package deployment, project organization, etc. labels Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Development issues: package deployment, project organization, etc. enhancement New feature or request Schema Related to the EBML schemata
Projects
None yet
Development

No branches or pull requests

1 participant