pypi

Install python package from private pypiserver

穿精又带淫゛_ 提交于 2019-12-05 12:26:44
I have setup a pypiserver behind an nginx proxy which uses htpasswd for authentication. I am currently able to upload sdists, but I can't figure out how to download them. I want to be able to download them when running setup.py test and somehow by using pip . Is this possible? [distutils] index-servers = private [private] repository = https://example.com/pypi username = remco password = mypass To make it extra hard the server is currently using a non verified ssl connection. I tried the following setup based on http://pythonhosted.org/setuptools/setuptools.html#setuptools-package-index , but

Image in README.rst not displaying in pypi

这一生的挚爱 提交于 2019-12-05 02:28:11
I would like an image linked in my README.rst file to be displayed when I upload my package to PyPI. In my README I have: .. image:: example-python.png :height: 100px :width: 200px :scale: 100 % :align: center and in MANIFEST.in I have: # Include the image file include example-python.png Right now it's not displaying in testpypi. It shows up just fine on GitHub, however. Am I doing something wrong? In .. image:: example-python.png you use relative URL, i.e. a browser expects the image in the same directory as the package. I doubt it's possible to upload an image at PyPI. Upload it somewhere

reStructuredText: README.rst not parsing on PyPI

独自空忆成欢 提交于 2019-12-05 01:30:42
I have a Python project that is hosted on both Github and PyPI. On Github: https://github.com/sloria/TextBlob/blob/master/README.rst On PyPi: https://pypi.python.org/pypi/textblob My README.rst doesn't seem to be formatting correctly on PyPI, but it looks fine on Github. I have already read this , but I don't have any in-page links, so that's not the problem. You are using a newer text role, :code: . PyPI appears to only support docutils 0.8, with code and code-block added to the PyPI parser directly, which means that :code: is not supported. GitHub uses a newer version of docutils (0.9 or 0

How to upload new versions of project to PyPI with twine?

时光毁灭记忆、已成空白 提交于 2019-12-04 23:35:33
I've uploaded my Python package to PyPI. But now I made new version of my package and need to upload it. I tried to make same progress which I did when upload the package first time. but give me this error: HTTPError: 400 Client Error: File already exists. See https://pypi.org/help/#file-name-reuse for url: https://upload.pypi.org/legacy Now, how to upload new version without any error?! PyPI does not allow for the reuse of distribution filenames (project name + version number + distribution type). This ensures that a given distribution for a given release for a given project will always

Why is PyPi called the cheese shop?

扶醉桌前 提交于 2019-12-04 22:11:55
I was running through the tutorials to build a Python distro package yesterday and the PyPi site kept on being calling the Cheese Shop. Why is that? Following the fact that the name of the Python language is taken from the Monty Python comedy group, it's a reference to the " Cheese Shop " sketch they did. There have been other prominent Python projects that have used the same approach to select names ( Bicycle Repairman and Grail are the first that come to mind) Because it's where you get your eggs! Perhaps as an antithesis for this . (batteries included ;-). 来源: https://stackoverflow.com

Custom location for .pypirc file

我与影子孤独终老i 提交于 2019-12-04 16:16:32
问题 Does setuptools allow for the .pypirc file to be specified in a custom location rather than $HOME/.pypirc ? I'm setting up a jenkins job to publish to an internal repository, and want the .pypirc file to be inside the job's workspace. 回答1: This is doable by overloading the default command classes used for communication with the PyPI or your custom repository server. This can be done in your setup.py script. Let the code do the talk first: # this is your project's setup.py script import os

Is PyPI case sensitive?

故事扮演 提交于 2019-12-04 15:03:31
问题 How does PyPI handle case sensitivity? For example, this SO question documents PyPI refusing a new package foobar if FooBar already exists. Running pip against pypi.python.org seems to convert to the canonical case for a package: $ pip install django Downloading/unpacking django Downloading Django-1.7.tar.gz (7.5MB): 7.5MB downloaded Alternatively: $ pip install Django Downloading/unpacking Django Downloading Django-1.7.tar.gz (7.5MB): 7.5MB downloaded However, only some files seem to be in

How to disable uploading a package to PyPi unless --public is passed to the upload command

假装没事ソ 提交于 2019-12-04 13:47:36
问题 I'm developing packages and uploading development/testing/etc versions of my packages to a local devpi server. In order to prevent an accidental upload to PyPi, I'm adopted the common practice of: setup(..., classifiers=[ "Programming Language :: Python", "Programming Language :: Python :: 2", "Programming Language :: Python :: 2.7", "Private :: Do not Upload" ], ...) which works great, but what about when I'm finally ready to upload the package to PyPi? I've come up with a totally ugly, but

Include *.pyd files in Python Packages

◇◆丶佛笑我妖孽 提交于 2019-12-04 11:07:59
I have a python module module.pyd that works pretty fine once it is put manually onto the site-packages of python installation folder. The problem starts when I upload my solution to a cloud enviroment, the buildpack requests that I pass every module as a package to be installed with pip install module . I ve created a folder with a simple __init__.py file that just imports everything of the module.pyd so that my module is treated like a folder. Then I read here http://peterdowns.com/posts/first-time-with-pypi.html how to upload my own module and I succeeded, but when I install my module, the

PyPI 400 upload error

一世执手 提交于 2019-12-04 10:15:45
问题 I created a package in PyPI named virtdc. I made some changes and uploaded 2 different versions 0.1.0 and 0.1.1. Now I deleted version 0.1.1 through the PyPI web interface and try to upload again with the same version number. It is giving me error as follows ... Writing virtdc-0.1.2/setup.cfg Creating tar archive removing 'virtdc-0.1.2' (and everything under it) running register Registering virtdc to http://pypi.python.org/pypi Server response (200): OK running upload Submitting dist/virtdc-0