Log file Viewer

[00:07:02] <redj> ngoldbaum: I've updated the gist (https://gist.github.com/redj/43e0585997fa39b9cc1775a550456b04) with the MANIFEST.in I'm currently testing with...

[00:07:34] <redj> but it just gives additional warnings like this:

[00:07:34] <redj> warning: no previously-included files found matching '*.3ds'

[02:35:32] <dfee> well i messed up. i deleted a dist from pypi, and now i can't upload a replacement. any ideas about what I should do?

[02:38:03] <ngoldbaum> cut a new release

[02:38:05] <tdsmith> cut a new version!

[02:38:20] <ngoldbaum> declare that release hopelessly broken and hope no one notices and makes fun of you

[02:38:28] <ngoldbaum> (we all cut broken releases)

[02:38:50] <tdsmith> you can use a .postN version -- something like 1.2.3.post0 -- if you want to indicate that it's not a new patch release.

[02:38:54] <dfee> am i supposed to manually rename the file so it has a build_tag? https://www.python.org/dev/peps/pep-0427/#file-name-convention

[02:39:51] <dfee> that seems like a solution. but i don't know if i'm supposed to do that via some `python setup.py bdist_wheel --set-a-build-tag-damnit 42` ...

[02:40:21] <tdsmith> i'm not sure i've seen wheel versions used in the wild. that won't help you with sdists, in any case

[02:40:48] <ngoldbaum> yeah, you change the version number by tagging a new commit

[02:40:53] <ngoldbaum> and updating the version numbers in the code

[02:41:12] <ngoldbaum> (it's also possible to do this without actually encoding the version numbers in the code by using e.g. coveralls)

[02:41:26] <ngoldbaum> and then generate a new sdist and wheels with the new tag

[02:41:33] <ngoldbaum> err, not coveralls sorry

[02:41:35] <ngoldbaum> versioneer

[02:41:36] <dfee> ngoldbaum: i have a version specified in my setup.cfg (literally [metadata] version=v18.5.0)

[02:41:43] <ngoldbaum> i was having a different conversation about coveralls

[02:42:01] <dfee> but version and build-tag seem to be different

[02:42:09] <ngoldbaum> build-tag?

[02:43:15] <dfee> ngoldbaum: yeah it's defined in the PEP where i linked

[02:43:19] <dfee> anyway that seemed to work.

[02:44:11] <ngoldbaum> ah, the build tag wouldn't matter

[02:44:25] <ngoldbaum> if you increment the version number

[02:44:30] <ngoldbaum> good deal

[02:44:55] <dfee> yeah but the build tag lets me not increment the version. as it's the only release, and it's using cal-ver, incrementing the build version would be strange

[02:44:58] <dfee> thanks!

[02:46:33] <tdsmith> as long as you only deleted a wheel

[08:31:14] <Guest91482> Hi, there. There is a bug fix for "rfc3986 1.1.0" within https://github.com/python-hyper/rfc3986

[08:31:58] <Guest91482> Wondering if it could be updated to https://pypi.org/project/rfc3986/ for download. Thank you very much. Have a good one.

[09:59:50] <njs> Guest91482: are you asking someone to publish a new release of rfc3986 on pypi? no-one here can do that; it's up to the package authors. I'd suggest filing an issue on the repo.

[10:01:55] <Guest91482> oh, thanks for that. :-)

[14:38:51] <FunkyBob> morning, all

[14:41:50] <FunkyBob> is there yet an established process for claiming an orphanaed package name? Specifically, "paws" has been claimed, but never had a release... and this isn't a recent thing

[14:44:04] <ngoldbaum> FunkyBob: yup, https://www.python.org/dev/peps/pep-0541/

[14:44:29] <ngoldbaum> right now the process is to open an issue at https://github.com/pypa/warehouse asking to claim the name

[14:44:37] <ngoldbaum> it may take a while for someone to get back to you

[14:44:41] <FunkyBob> thanks