PyPi does not allow duplicate file names -- this makes lots of sense,
because you really don't want people to go to PyPi one day and grab a file,
and then go there another day, grab a file with exactly the same name, and
have it be a different file.
We are all too human, and make mistakes when doing a release. All to often
someone pushed a broken file up to PyPi, often realizes it pretty quickly
-- before anyone has a chance to even download it (or only the dev team as,
In fact, I was in a sprint last summer, and we decided to push our package
up to PyPi -- granted, we were all careless amateurish noobs, but we ended
up making I think 4! minor version bumps because we had done something
stupid in the sdist.
Also -- the latest numpy release got caught in this, too:
* We ran into a problem with pipy not allowing reuse of filenames and a
resulting proliferation of *.*.*.postN releases. Not only were the names
getting out of hand, some packages were unable to work with the postN
So -- I propose that PyPi allow projects to replace existing files if they
REALLY REALLY want to.
You should have to jump through all sorts of hoops, and make it really
clear that it is a BAD IDEA in the general case, but it'd be good to have
it be possible.
After all -- PyPi does not take on responsibility for anything else about
what's in those packages, and Python itself is all about "we're all
consenting adults here"
I suppose we could even put in some heuristics about how long the file as
been there, how many times it's been downloaded, etc.
Just a thought.....I really hate systems that don't let me roll back
mistakes, even when I discover them almost immediately...
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
I've got two projects: mynamespace.myprojectA and mynamespace.myprojectB
myprojectB depends on myprojectA. I'm using setuptools 0.6c8 to manage both
Both projects are registered using 'setup develop'. Both projects are
accessible from an interactive interpreter:
PS C:\Users\me\projects> python
Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)]
Type "help", "copyright", "credits" or "license" for more information.
>>> import mynamespace.myprojectA
>>> import mynamespace.myprojectB
>>> from mynamespace.myprojectA import mymoduleZ
However, when I run 'setup test' in myprojectB, the tests fail with
File ".mymoduleZ.py", line NNN, in [some context]
from mynamespace.myprojectA.mymoduleZ import MyClassC
ImportError: No module named myprojectA.mymoduleZ
In setup.py, the test_suite is nose.collector.
I searched and couldn't find anyone else with this problem. Is this a
supported configuration? Is there something I can do to make tests work
with interdependent projects with the same root namespace?
If there's not something obvious I should be doing differently, I'm happy to
put together a minimal test case that reproduces the problem. Any
suggestions are appreciated.
Jason R. Coombs
I’m looking for anyone how has built something interesting using the PyPI Big Query public dataset that’s documented at packaging.python.org/guides/analyzing-pypi-package-downloads.
There are some changes that are coming up that we’d like to preview for users that are actively using the dataset.
If that’s you, send a note to bigquery-feedback(a)pypi.org with how you’ve been using the dataset. I’ll get back to you with information on the upcoming changes and will select a few projects to feature in the announcement of the new changes.
-Ernest W. Durbin III
Director of Infrastructure
Python Software Foundation
I have a pipfile like this.
I would like to install python-apt library but not from pypi but from the
This python library is no longer supported on pypi but is supported in the
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true
ansible = "==2.8.4"
ansible-lint = "*"
molecule = "*"
docker-py = "*"
python_version = "3"
Hey all --
With Sumana's help, I've been working to get the next pipenv release out
by the end of the month. As some of you may already know, I recently
changed jobs and am now working for Canonical where I have part of my
time allocated to open source work in general (and pipenv in particular).
The main pipenv release blockers have been fixes in andnew releases of
requirementslib, pythonfinder, pip-shims, and vistir, and merging
missing dependencies/imports.I've beenworking on these and should wrap
up this week.||
You can help in a few ways:
1. Look at the tracking issue for the new release
https://github.com/pypa/pipenv/issues/3369and speak up there if you know
of a release blocker that isn't in the list.
2. If you see me in #pypa-dev on Freenode IRC, feel free to ask me what
I'm working on. Sumana's been keeping me focused this month (and helped
me write up the tracking issue, and this email) and it's been helpful,
as I am juggling a lot of obligations and can get distracted.||
3. I could use help replying to new users' questions in pipenv GitHub
issues, so I can concentrate on the new release. If you'd like triage
permissions on the project please reach out, I'd be happy to give them.
4. Documentation! Pipenv documentation, now at
https://pipenv.pypa.io/,needs some serious rework. So if you have any
skills in this area,the project would really benefit from a critical
5. Make sure to say 'thanks' to Sumana if you see her on IRC, she is
responsible for moving this release forward and is pretty great!
I'd appreciate the help.
-Dan Ryan (techalchemy)
|:| You can look at
more context on why we've been delayed on a new release since November 2018.
||: Iacknowledge that I've been super behind on this release,but I
also have moved, had a fire in my new house, changed jobs, etc., and am
onlynowsettling into my new role where I finally am paid to spend some
time on pipenv.So, after this release is out, I hope to get back to
helping new contributors more so we can promote some more
co-maintainers, so this doesn't block releases again.
@techalchemy | Pipenv Maintainer