devpi | 易学教程

toxresult_upload permission in devpi index

阅读更多关于 toxresult_upload permission in devpi index

问题 I am using the Python devpi server, and when I create an index, it adds a default a setting acl_toxresult_upload=:ANONYMOUS: , but I cannot find out what it means. When I view the index in the web interface, it shows: permissions toxresult_upload Special: ANONYMOUS upload Users: my-user I googled it, but could not find any explanation of what it means. The only thing I could find was a python test that indicates it has something to do with uploading tests, but I'm not sure what that means

Difference between devpi and pypi server

阅读更多关于 Difference between devpi and pypi server

问题 Had a quick question here, am used to devpi and was wondering what is the difference between devpi and pypi server ? Is on better than another? Which of this one scale better? Cheers 回答1: PyPI (Python Package Index)- is the official repository for third-party Python software packages. Every time you use e.g. pip to install a package that is not in the standard it will get downloaded from the PyPI server. All of the packages that are on PyPI are publicly visible. So if you upload your own

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

阅读更多关于 How to disable uploading a package to PyPi unless --public is passed to the upload command

问题 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

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

阅读更多关于 How to disable uploading a package to PyPi unless --public is passed to the upload command

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 simple hack which requires that I define the classifiers as a global variable outside of the setup()