Pip install not working and PyPi info data not loading when whl file uploaded to artifactory.

[Laserwhit]

When I load other libraries (see my attached chardet-3.0.4-py2.py3-none-any.whl example) into artifactory and then click on the PyPi info I see what is shown in the attachment, valid PyPi information. I am then able to pip install the file from our internal artifactory server.
When I load deprecation version 2.0 everything works fine (see attachment).
But when I load deprecation versions after 2.0 (2.0.1 and 2.0.2) I don't get the PyPi information when clicking on the tab in artifactory (see attachment) and I am unable to access it from pip install.

[Laserwhit]

Also when you click on the Properties tab in deprecation 2.0 there are 4 properties specified: pypi.name: deprecation -> pypi.normalized.name: deprecation -> pypi.version: 2.0 -> pypi:summary: A library ...

These are also missing in 2.0.1 and 2.0.2. Not sure what is causing the libraries not to be visible from pip install but these are things I am noticing.

[Laserwhit]

The only thing I am noticing as I look at differences in the INFO files between 2.0 and 2.0.2 is that the following line exists in 2.0 and does not in 2.0.2:
Description-Content-Type: UNKNOWN
Reading the docs this shouldn't make a difference but there is a difference in behavior and this is the only thing that jumps out at me.

[briancurtin]

I installed the artifactory-oss docker image and have it running, but apparently it can't view packages, so I'm not entirely sure how to reproduce this.

Looking at the diff between 2.0 and 2.0.2 I would guess it might be that artifactory doesn't know how to process the project_urls that were added in 2.0.1? They turn into Project-URL metadata in the PKG-INFO file, with one entry per URL. It seems like documentation and examples for project_urls in setuptools and Project-URL in the package metadata didn't really show up until the end of Feburary, so this is probably still new to a lot of people. I only found out about it a few weeks ago when I added it, because someone mentioned to me that this package didn't have a link to GitHub anywhere on the PyPI page, but I also wanted to be linking to the docs as well, so project_urls solved that.

Are you able to try adding some recent Flask packages to your artifactory and see if they work? It looks like they started using project_urls a few days ago in 1.0.0 but they were not using it in 0.9. If you happen to be able to see 0.9 work but 1.0 doesn't work, I think this is an artifactory problem.

If those two Flasks work fine, then I don't entirely know where to go from here, but I'll ask around and see if anyone knows what might be going on.