Log file Viewer

[13:31:12] <jellycode> toad_polo - artifactory

[13:31:51] <toad_polo> Haha. Amazing coincidence.

[13:32:11] <toad_polo> I saw your message like minutes after writing up the problem.

[13:32:35] <toad_polo> Using setup.py upload should work for now since setup.py upload has the complementary bug.

[13:34:25] <toad_polo> I don't know if Artifactory actually uses the metadata you upload there. The fact that setup.py doesn't do it correctly means that it screws up PyPI when you don't use twine.

[13:44:40] <jellycode> Well, I was using artifactory for a bit, it was fine, then I believe the metadata changed to 2.0 and artifactory did not support, so I reported to Jfrog, and they told me there's a patch in the pipeline for it... and i thought it was all resolved.

[13:56:11] <toad_polo> Yeah, I'm no Artifactory expert or anything, I just know that we upgraded artifactory recently to get the support for pypi.org and this is happening (not sure if it was happening before as well).

[13:56:20] <toad_polo> I went through and patched twine to start sending metadata_version 1.0 and it started working.

[14:02:33] <toad_polo> For those on the original CC e-mail but not yet subscribed to pypa-commiters: https://mail.python.org/mm3/archives/list/pypa-committers@python.org/thread/PSNNUC3GQNOP4VTSHIJKBB25QOMOQZTR/

[14:02:48] <toad_polo> Looks like we have a strong contender for BDFN, please weigh in.

[17:00:56] <dwighthubbard> Artifactory is uploading the packages but it then uses properties to store the package normalized name, it does that by parsing the metadata and it currently doesn't understand the new metadata format.

[17:01:26] <dwighthubbard> They evidently don't have the concept of running tests of things against test versions of python functionality.

[18:07:24] <toad_polo> dwighthubbard: I think it's actually as simple as it has a pinned upper limit on the metadata version.

[18:07:59] <toad_polo> Because the upload succeeds if you patch twine to always send `metadata_version` as "1.0"

[18:08:24] <dwighthubbard> The workaround is to pin the version of setuptools to one that doesn't use the metadata format or to patch twine.

[19:55:20] <dwighthubbard> Patching twine would also work

[20:00:26] <toad_polo> I would prefer to patch twine, though I guess Artifactory will fix this in Q2.

[23:13:00] <njs> toad_polo: ugh wait is this another mailing list I should be subscribed to

[23:41:20] <Schwarzbaer> Soooo, pip, pipyserver, devpi, twine, optionally warehouse, and now artifactory. Are there any other package-related tools that I should be aware of?

[23:42:31] <toad_polo> Artifactory doesn't really fit in that list.

[23:43:24] <Schwarzbaer> Yeah, now that I watch their sales blurb, it sounds more like a build/test/deploy server.

[23:45:53] <Schwarzbaer> Still, any Python-related tools that *should* be on that list?