You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this comment, @RonnyPfannschmidt reported that when the metadata for a package appears more than once in sys.path, that metadata gets emitted for each instance in which it appears.
I'm not sure what's to be done in this case, but I wanted to split it out as a separate issue from the issue caused by the presence of both importlib.metadata (Python 3.8) and its backport (importlib_metadata), which was addressed in #91.
Ronny, can you describe more about the conditions that cause this behavior to happen? What distro, how did you create the virtualenv? Would you consider supplying a Docker script that builds up such an environment?
In GitLab by @jaraco on Nov 30, 2019, 20:53
In this comment, @RonnyPfannschmidt reported that when the metadata for a package appears more than once in
sys.path, that metadata gets emitted for each instance in which it appears.I'm not sure what's to be done in this case, but I wanted to split it out as a separate issue from the issue caused by the presence of both
importlib.metadata(Python 3.8) and its backport (importlib_metadata), which was addressed in #91.Ronny, can you describe more about the conditions that cause this behavior to happen? What distro, how did you create the virtualenv? Would you consider supplying a Docker script that builds up such an environment?