Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation about .pypirc file #23

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add documentation about .pypirc file #23

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Oct 16, 2016

The Publishing On PyPI section should explain how repositories are resolved.
Without explicitly configuring .pypirc file, the default pypi repository will
be resolved as 'https://upload.pypi.org/legacy/', which is obsolete.

The improved content demonstrates a simple .pypirc file with valid pypi and
pypitest respositories. It also adds repository flag to package commands (e.g.,
register, upload) to demonstrate how user can switch between repositories.

The `Publishing On PyPI` section should explain how repositories are resolved.
Without explicitly configuring .pypirc file, the default pypi repository will
be resolved as 'https://upload.pypi.org/legacy/', which is obsolete.

The improved content demonstrates a simple .pypirc file with valid pypi and
pypitest respositories. It also adds repository flag to package commands (e.g.,
register, upload) to demonstrate how user can switch between repositories.
@storborg
Copy link
Owner

Sorry for not responding to this sooner. I can't seem to replicate the above issue: that is, using a plain configuration, with or without an existing .pypirc, works just fine. Is that behavior platform or version specific somehow?

@ghost
Copy link
Author

ghost commented Oct 26, 2016

Oh, no problem. I am very busy at work as well :(

Maybe I try again to confirm that whether it is platform specific or not.
Also we may put my change into FAQ in case someone encounter again and have
a cross link to that FAQ page by saying in case you encounter this issue
please check this. What do you think?


Sent from my Samsung Mobile

On 24 Oct 2016 03:25, "Scott Torborg" notifications@github.com wrote:

Sorry for not responding to this sooner. I can't seem to replicate the
above issue: that is, using a plain configuration, with or without an
existing .pypirc, works just fine. Is that behavior platform or version
specific somehow?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACB5MrDxTELFC4-SFhTtXjDm5-5AK00yks5q27TBgaJpZM4KX4tZ
.

@storborg
Copy link
Owner

Yeah, let's investigate a bit more. What platform were you seeing that issue on? I generally use Ubuntu 14.04/16.04 and OS X, and haven't seen that on either.

@ghost
Copy link
Author

ghost commented Oct 27, 2016

I have tried with latest ubuntu, it works fine. I presume my setup was too old. You can ignore this pull request. Thank you for your time.

@ghost
Copy link
Author

ghost commented Oct 27, 2016

I will send the details asap.


Sent from my Samsung Mobile

On 27 Oct 2016 11:33, "Scott Torborg" notifications@github.com wrote:

Yeah, let's investigate a bit more. What platform were you seeing that
issue on? I generally use Ubuntu 14.04/16.04 and OS X, and haven't seen
that on either.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACB5MjNH8quDzbY9wfLqVjZ8vsU2dlDMks5q4BuhgaJpZM4KX4tZ
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant