Log file Viewer

[01:53:09] <marnanel> why is it that the links in the project description at https://test.pypi.org/project/kepi/0.4.5/ all 404? "docs/roadmap.md" is in the package.

[01:58:00] <nedbat> marnanel: pypi doesn't serve files from your repo

[02:12:54] <marnanel> nedbat: thanks. So should I not put links in the README?

[02:13:18] <nedbat> marnanel: you publish your docs elsewhere, and put links that go there.

[02:13:41] <marnanel> nedbat: thank you!

[12:29:51] <Nekokatt> hello, I was wondering if there is any info on when PyPI will be rebuilt with the latest TROVE classifiers package?

[12:33:42] <nedbat> Nekokatt: which classifier do you need?

[12:34:01] <nedbat> (or, I probably am misunderstanding the question)

[16:20:48] <tos9> You're waiting for 3.10 I assume?

[16:21:08] <tos9> (I don't know the ansewr but I'd be prett sure it's "very soon" if not already?)

[16:21:13] <tos9> The PR was merged IIRC.

[16:22:13] <tos9> Nekokatt: Yeah, seems like it's already been deployed.

[16:23:47] <nedbat> tos9: i checked this morning, 3.10 is there: https://github.com/nedbat/coveragepy/commit/0b1dd531f23d8ba313ee685b156b07f76fa680d5

[16:24:16] <tos9> Heh, you test on 3.10, nice, power to you

[16:24:20] <tos9> Even testing on 3.9 is a PITA.

[16:27:02] <nedbat> tos9: i started today :) but pypy is becoming the big PITA

[16:27:54] <tos9> nedbat: To me they're pains for the same reason. The scientific stack still being awful to build when wheels aren't present.

[16:28:17] <nedbat> i can't even get a pypy2 with ssl on my mac

[16:28:20] <tos9> It so happens that's always the case for PyPy whereas at least for CPython like 6 months into a release wheels pop up

[16:28:34] <tos9> nedbat: hrm? Why not?

[16:28:37] <tos9> Use brew, not pypy.org

[16:28:53] <tos9> (Or if you're doing that already yeah what's happening?)

[16:28:58] <nedbat> i've been using pyenv for CPython. brew seems to bork ssl too

[16:29:01] <tos9> We should kill the pypy.org builds for macOS.

[16:29:48] <tos9> Yeah I have no idea about pyenv. But I have no issues (and have never had any issues) with brew + pypy + ssl for all Python versions.

[16:30:00] <tos9> If you use pyenv probably make sure you put openssl on your LIBRARY_PATH and LD_LIBRARY_PATH

[16:30:15] <tos9> (or maybe make sure the reverse that you don't do that if pyenv wants to do it, who even knows)

[16:37:48] <nedbat> this is what i mean...

[21:37:01] <toad_polo> [tos9](https://matrix.to/#/@freenode_tos9:matrix.org): If it takes you a while then it might be worth throwing 3.9 wheels in devpi for the scientific python stack.

[21:38:23] <toad_polo> I wonder if we'd get better adoption of pre-release wheels if there were a way to replace existing wheel files built against an RC after the fact.

[21:39:28] <toad_polo> Another interesting solution would be a publicly hosted PyPI mirror similar to piwheels

[21:42:53] <toad_polo> Not intended to be immutable, wheels re-built against 3.(n + 1) every week or something for a certain list of packages, removed when an upstream wheel is available.

[21:43:32] <toad_polo> I mean it's pretty easy to do yourself locally, but I wonder if people would find a public version useful.

[22:51:46] <tos9> toad_polo: yes I think that's pretty critical

[22:51:55] <tos9> (public wheel building infra for packages/configurations that are missing it)

[22:52:10] <tos9> in fact that was the one thing I wanted to explore sponsoring at $WORK in better economic times...