We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
the fix for #542 in #551 was backwards incompatible and thus not fit for the patch release 4.2.2 and reverted in #595
this issue is a reminder to either replay bccc761 and ae1f639 on top of 5.0.0-dev or maybe drop the unicode base-class for Namespace altogether...
Namespace
@gromgull any preference?
The text was updated successfully, but these errors were encountered:
I would drop unicode for namespace, I cannot really see any use-cases why it is useful that it's a subclass at all?
Then let ClosedNamespace inherit from Namespace
ClosedNamespace
Sorry, something went wrong.
👍 Totally agree.
please have a look at #597
I cannot really see any use-cases why it is useful that it's a subclass at all?
How does one filter for "properties" from DCTERMS namespace if not by:
DCTERMS
for p, o in g.predicate_objects(s): if p.startswith(DCTERMS): ...
joernhees
Successfully merging a pull request may close this issue.
the fix for #542 in #551 was backwards incompatible and thus not fit for the patch release 4.2.2 and reverted in #595
this issue is a reminder to either replay bccc761 and ae1f639 on top of 5.0.0-dev or maybe drop the unicode base-class for
Namespace
altogether...@gromgull any preference?
The text was updated successfully, but these errors were encountered: