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
We are currently having an issue with liccheck and version 17.3.0 of pyrsistent.
Liccheck always flags the package as unknown, due to the fact that there is a \r in the string, which is most likely an artifact from the Windows line break \r\n:
Other packages using the MIT license are parsed just fine.
I dug a bit into the metadata parsing and found that the metadata for pyrsistent: 17.3.0 indeed contains \r\n linebreaks, while all other packages have \n in their metadata. It probably got compiled on Windows with faulty settings regarding the line endings.
Is it possible to adjust the metadata parsing to support Windows line endings?
The text was updated successfully, but these errors were encountered:
We are currently having an issue with
liccheck
and version17.3.0
ofpyrsistent
.Liccheck always flags the package as unknown, due to the fact that there is a
\r
in the string, which is most likely an artifact from the Windows line break\r\n
:Other packages using the MIT license are parsed just fine.
I dug a bit into the metadata parsing and found that the metadata for
pyrsistent: 17.3.0
indeed contains\r\n
linebreaks, while all other packages have\n
in their metadata. It probably got compiled on Windows with faulty settings regarding the line endings.Is it possible to adjust the metadata parsing to support Windows line endings?
The text was updated successfully, but these errors were encountered: