pypi

I am a newb to PyPI...so let me qualify with that. I am trying to put a package on PyPI but having a bit of trouble when I try to install it with pip. When I upload the file to PyPI, I get a warning (but the setup.py script finishes with not fatal errors and a 200 status): 'my_package/static/my_folder' not a regular file -- skipping And then when I go to install it in pip, I get an error: "error: can't copy 'my_package/static/my_folder': doesn't exist or not a regular file. From other answers on SO, I've tried changing up my MANIFEST.in and my setup.py files, with no luck. Here is my current

I was wondering what is the best procedure or practices for releasing a new python package version on pypi and github. For example, is this the typical workflow a major python package would follow? On master branch, increment version number Set version='1.5.0' in setup.py Set __version__ = '1.5.0' in package __init__.py Update CHANGELOG.md with new version Run tox locally to verify package Push changes git push origin master Create tag git tag v1.5.0 -m "Release v1.5.0" Push tag git push origin v1.5.0 Wait for Travis CI build to finish. Build package python setup.py sdist bdist_wheel Verify

My problem is that when I upload my Python package to PyPI, and then install it from there using pip, my app breaks because it installs my files into completely different locations than when I simply install the exact same package from a local sdist. Installing from the local sdist puts files on my system like this: /Python27/ Lib/ site-packages/ gloopy-0.1.alpha-py2.7.egg/ (egg and install info files) data/ (images and shader source) doc/ (html) examples/ (.py scripts that use the library) gloopy/ (source) This is much as I'd expect, and works fine (e.g. my source can find my data dir,

I am trying to use twine to publish my first python package on pypi (of course will add on test-pypi first). I followed the official guideline on https://packaging.python.org/tutorials/packaging-projects/ . But for some reason, twine is not found or not properly installed. I installed twine using: pip install twine "pip list" says twine is installed on pip. After I upgraded twine and everything, when I tried to run: twine upload --repository-url https://test.pypi.org/legacy/ dist/* then it says that twine is not found at all: -bash: twine: command not found . My system is mac (high sierra) and

I have a package on PyPi and when preparing a new release I build the source distribution, build the wheel and upload, all with setuptools. However, I've found it only uploads the wheel for the Python version used in the upload command ( python and python3 ). Here are the steps I'm taking: python3 setup.py sdist python3 setup.py bdist_wheel --universal python3 setup.py sdist bdist_wheel upload According to the Python Packaging User Guide : "Universal Wheels" are wheels that are pure python (i.e. contains no compiled extensions) and support Python 2 and 3 So that seems to be the right thing for

What's the magic " python setup.py some_incantation_here " command to upload a package to PyPI, in a form that can be downloaded to get the original package in its original form? I have a package with some source and a few image files (as package_data). If I do " setup.py sdist register upload ", the .tar.gz has the image files excluded. If I do " setup.py bdist_egg register upload ", the egg contains the images but excludes the setup.py file. I want to be able to get a file uploaded that is just the entirety of my project -- aka " setup.py the_whole_freaking_thing register upload ". Perhaps