Repository URL weirdness #206
It seems there might be some weirdness with defining the pypi repo url related to #203 changes which exist in
With the following variables set:
However, if I rm the
From this, it seems like twine won't even read the variables if a
Additionally, if I have the following variables defined:
Well ok...what if just
Either with or without a
I receive an error about a problem with configuration:
There is definitely something going on here. If all I should need, given I don't have a
I want to thank @sigmavirus24 for his work on getting this feature merged and in 1.8.1. Hopefully with a few minor changes, we can make it work swimmingly for everyone ;)
I looked a bit into this and the issue lies in the following problem: If you don't have a
It will then go to
The fix pretty much depends on the behaviour expected from the program. I feel like it would be expected that
I also feel like you shouldn't be removing the
Having said all of that, I created a simple commit that only changes the behaviour of having the URL take precedence over a repo name. This clearly changes the behaviour of the program and is nut just a bugfix. That is, if you rely on this where you provide
@sigmavirus24 you implemented this feature it appears so maybe you could chime in on whether you wanted this to be in here explicitly. If the decision is to make the URL only a fallback, then we could discuss only overriding with the URL if the name for the repo is the default.
In any case, I would like to get this feature improved, because the current fix basically relies on creating dummy files or providing invalid parameters and none of that is very clean. I'll happily provide PRs for expected behaviour :)
@InAnimaTe thx for your export tip, it worked for me where neither the setting the proper uri in .pypirc and removing the file worked.
imho this kind of issues are annoying as they are noticed... at release time ;)
We could manage to:
referenced this issue
Feb 22, 2017
referenced this issue
Feb 25, 2017
Thank you @zirpu , your comment about non-accepted characters helped me!
It may be worth mentioning that I had this issue when trying to use Travis CI to deploy to PyPi (https://github.com/egnyte/gitlabform/blob/master/.travis.yml).