Cannot get metadata from .egg-info files about importlib_metadata

[jaraco]

In GitLab by @chrisjbillington on Feb 10, 2019, 23:18

changed the description

[jaraco]

In GitLab by @chrisjbillington on Feb 11, 2019, 02:48

So it turns out it has nothing to do with pyserial's name.

It's the fact that my .egg-info for pyserial is a file, and not a directory. Over on Anaconda Python on Windows, it's a folder. The single file on linux corresponds to the PKG-INFO file within the folder.

Reading up on this, it seems that .egg-info is allowed to be a file and so it can't be assumed it's a directory. So this looks like maybe an invalid assumption being made by importlib_metadata, if I'm understanding correctly.

[jaraco]

In GitLab by @chrisjbillington on Feb 11, 2019, 03:37

changed title from Can{-'t get metadata for pyserial-} to Can{+not get metadata from .egg-info files+}

[jaraco]

In GitLab by @chrisjbillington on Feb 11, 2019, 04:23

mentioned in merge request !38

[jaraco]

In GitLab by @tliu61 on Feb 24, 2019, 04:27

Yes, according to The Internal Structure of Python Eggs, the Project Metadata section third paragraph:

Because it's possible for this (PKG-INFO) to be the only metadata file included, .egg-info format eggs are not required to be a directory; they can just be a .egg-info file that directly contains the PKG-INFO metadata.

[jaraco]

In GitLab by @warsaw on May 6, 2019, 14:58

.egg-info files are produced by distutils, directories by setuptools.

[jaraco]

In GitLab by @Lawouach on May 7, 2019, 13:22

Hi all, I wonder if I see the same issue here pytest-dev/pluggy#205

What would be the best way to reproduce in a simple fashion though?

[jaraco]

In GitLab by @warsaw on May 7, 2019, 15:50

mentioned in merge request !57

[jaraco]

In GitLab by @warsaw on May 7, 2019, 20:20

closed via merge request !57

[jaraco]

In GitLab by @warsaw on May 7, 2019, 20:20

mentioned in commit 2ca4591