summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornicholascar <nicholas.car@surroundaustralia.com>2021-12-10 23:00:08 +1000
committernicholascar <nicholas.car@surroundaustralia.com>2021-12-10 23:00:08 +1000
commit5db73199f0036cfb68c5c68e99ff31d422f5261b (patch)
treefb2fd8640b1290cca68473de88f79bb958ce0a20
parent9379a69d6ec6e18819aa0c5a0d54849e7abb8223 (diff)
downloadrdflib-5db73199f0036cfb68c5c68e99ff31d422f5261b.tar.gz
demo 980 resolutionissue_980
-rw-r--r--test/test_980.py28
1 files changed, 28 insertions, 0 deletions
diff --git a/test/test_980.py b/test/test_980.py
new file mode 100644
index 00000000..3c60a849
--- /dev/null
+++ b/test/test_980.py
@@ -0,0 +1,28 @@
+from rdflib import Graph
+
+
+def test_980():
+ """
+ The problem that this test ensures rdflib solves is that, previous to PR #1108, the
+ parsing of two triples with the same n-triples Blank Nodes IDs, here _:0, would
+ result in triples with the same rdflib internal BN IDs, e.g.
+ rdflib.term.BNode('Ne3fd8261b37741fca22d502483d88964'), see the Issue #980. They
+ should have different IDs.
+ """
+ graph1 = """
+ _:0 <http://purl.obolibrary.org/obo/RO_0002350> <http://www.gbif.org/species/0000001> .
+ """
+ graph2 = """
+ _:0 <http://purl.obolibrary.org/obo/RO_0002350> <http://www.gbif.org/species/0000002> .
+ """
+
+ g = Graph()
+ g.parse(data=graph1, format="nt")
+ g.parse(data=graph2, format="nt")
+
+ subs = 0
+ for s in g.subjects(None, None):
+ subs += 1
+
+ # we must see two different BN subjects
+ assert subs == 2