Handling of multiple variables of the same name in Python scripts is untested about pip-run HOT 3 CLOSED

Indeed, it passes! That's why I said #102 preserves the behavior of handling multiple assignments, and does not alter it.
I saw a missing test rather as a coverage issue, not an undefined behavior.

Looking at

Which is why maybe it's a better idea to actually make _read safe and precisely describe the cases it supports? This is what #102 tried to do, but at the cost of expanding the implementation to imperative approach.

The callee of that function just so happened to suppress ValueError, so that's why I thought the concern was addressed since the beginning.

from pip-run.

Also, I'll want to test to confirm what is the current behavior.

The following test passes, so the current behavior is to silently ignore both:

diff --git a/tests/test_scripts.py b/tests/test_scripts.py
index 877c0a5..0326b4c 100644
--- a/tests/test_scripts.py
+++ b/tests/test_scripts.py
@@ -56,6 +56,15 @@ class TestSourceDepsReader:
         )
         assert scripts.DepsReader(script).read() == ['foo']
 
+    def test_duplicate_definition(self):
+        script = textwrap.dedent(
+            """
+            __requires__=['foo']
+            __requires__=['bar']
+            """
+        )
+        assert scripts.DepsReader(script).read() == []
+
     def test_reads_files_with_multiple_assignment(self):
         script = textwrap.dedent(
             """

from pip-run.

I've gone ahead and pushed that test, making it an explicitly-tested expectation.

Indeed, it passes! That's why I said #102 preserves the behavior of handling multiple assignments, and does not alter it.
I saw a missing test rather as a coverage issue, not an undefined behavior.

Thanks. Yeah, that was my mis-read on the intention there.

from pip-run.