Open MasonEgger opened 6 years ago
I actually have the opposite problem. It's not throwing an error, and appears to be failing silently, as the package is not uploaded to pypi
$ flit publish --repository testpypi
Found 3 files tracked in git I-flit.sdist
Writing generated setup.py I-flit.sdist
Built sdist: dist\brendan_pack-0.1.0.tar.gz I-flit_core.sdist
Copying package file(s) from C:\Users\XXX\AppData\Local\Temp\2\tmptbsqkd5u\brendan_pack-0.1.0\brendan_pack.py I-flit_core.wheel
Writing metadata files I-flit_core.wheel
Writing the record of files I-flit_core.wheel
Built wheel: dist\brendan_pack-0.1.0-py2.py3-none-any.whl I-flit_core.wheel
Using repository at https://test.pypi.org/legacy I-flit.upload
Uploading dist\brendan_pack-0.1.0-py2.py3-none-any.whl... I-flit.upload
Package is at https://test.pypi.org/project/brendan_pack/ I-flit.upload
Using repository at https://test.pypi.org/legacy I-flit.upload
Uploading dist\brendan_pack-0.1.0.tar.gz... I-flit.upload
Package is at https://test.pypi.org/project/brendan_pack/ I-flit.upload
@bpabel your package appears to be there now at the address shown in the output: https://test.pypi.org/project/brendan_pack/
Is it possible that you looked at the main PyPI site? test.pypi.org is separate, so uploads there won't show up on regular PyPI. Or perhaps something was cached somewhere, so the change didn't show up immediately?
@takluyver Yes, it uploaded after I changed the pypi path to include the trailing slash, so that's why those packages are there now.
When trying to upload to https://test.pypi.org/legacy a stack trace is thrown stating the url is not found. If a trailing / is appended as such https://test.pypi.org/legacy/ the issue is no longer present.
[testpypi] repository = https://test.pypi.org/legacy username = Zelgius # Replace with your TestPyPI username