tree 08e725b7d06a6ceb75dd95814ead91e61491e9c4
parent f9d6189b6320c1852078a16434846e69268d187e
author Richard Levasseur <rlevasseur@google.com> 1702943457 -0800
committer GitHub <noreply@github.com> 1702943457 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlgNrxCRBK7hj4Ov3rIwAAR78IAFoR33oKaN0Inhew7BT8zNYI
 6vR7TU0jGxn8a9nVXqy7jOP3HvDtMY8jtG+Hkjl/ktE7EQvoq0GrVXaCbbsHTRuy
 pxIqKjlwLtlrJXWIipdweLpmupTzPfnTdvDRTfenNMIxeTmnadBs6DcDaAFU1kyZ
 GhC+YiNwn2iZ/vGW34hinYGID5QMmb6q0hIgM9PQ7HSsCsPLuFW57JwnyJRD4OE4
 nEXthf8x7ag5K7Y/W7xQVbt4WGJUK9gWG3sxsP7jHfIxf8O4g805zi+EXN6JnT7t
 C9nwkOMyVCU2i3jhNgmF8EfF60puWoqMJj8tJV54yAO3nYHUYXM0PESHJ42BTS0=
 =O8fM
 -----END PGP SIGNATURE-----
 

fix(bzlmod pip.parse): allow requirements with duplicate package lines (#1620)

Requirements files are permitted to have duplicate lines for the same
package. An example
of this is having separate lines for a package and its extras. When we
parse requirements,
the parser discards the "extra" portion of the entry and returns a list
of all the packages
as-is. When a repository is created for each entry, this means the same
name is used for
multiple repositories.

Under WORKSPACE builds, duplicate repository names aren't an error. It
appears that last
defined repo takes affect. Under bzlmod, duplicate repo names are an
error.

To fix, mimic the last-defined-wins behavior in bzlmod by using a map to
dedupe the package names.

Fixes https://github.com/bazelbuild/rules_python/issues/1615