Pypi? #2

Closed
lyda opened this Issue Feb 23, 2013 · 14 comments

Projects

None yet

4 participants

lyda commented Feb 23, 2013

There's an old, broken mockfs on pypi. Could this replace it?

Collaborator
davvid commented Feb 24, 2013

Interesting. That project is in no way related to this project. Thanks for the heads up. I could try uploading something to pypi but I don't know if it will let me.

lyda commented Feb 24, 2013

I doubt it will. Might be better to come up with a new name. How about "mockvfs" for "mock virtual filesystem?"

I've also submitted some changes to a similar effort from Google to update it for current versions of python as well as be a more standard python project: http://code.google.com/r/kevin-pyfakefs-pypi/source/list

Collaborator
davvid commented Feb 24, 2013
$ python setup.py register
running register
running check
Registering mockfs to http://pypi.python.org/pypi
Server response (403): You are not allowed to store 'mockfs' package information

If the other project is abandoned then I'm a little less compelled to change the name. Maybe you can talk to the author on pypi and ask them if we can be the new maintainers? In the very least we'll need to advertise that this project is newer and not the same as the one on pypi.

lyda commented Feb 24, 2013

The home page for the older mocks module is on launchpad: https://launchpad.net/mockfs

But the author is on github: @zyga.

I've sent him an email.

Contributor
zyga commented Feb 26, 2013

Hey, sorry for taking this long to work on this issue. I'm still pretty busy (it's a busy week at Canonical). I'm not opposed to allowing you to use mockfs assuming it does not collide with anything I may have used my tiny mockfs with before. I need to check if any active project still needs that.

Contributor
zyga commented Mar 19, 2013

Hey,

So we can do this:

  1. Ensure that old tarballs stay as they are on pypi
  2. Ensure that new mockfs has major version > than current pypi mockfs
  3. Release new mockfs on pypi

How do you feel about such approach?

Collaborator
davvid commented Mar 20, 2013

I recently tagged v1.0 and the pypi mockfs had v0.2 so I think we're good on 2. Keeping the historical tarballs around is no problem at all. My pypi username is "davvid" in case their interface allows adding other uploaders? Thanks @zyga.

Contributor
zyga commented Mar 20, 2013

You should now be able to upload, thanks

lyda commented Mar 20, 2013

Hurrah! Thanks guys!

lyda commented Mar 20, 2013

BTW, I don't see many people gpg signing their git tags or their pypi releases. From what I've read the pypi guys are slowly working on allowing people to verify signatures. It might be something to consider. I did it for my projects and it wasn't all that hard.

Collaborator
davvid commented Mar 23, 2013

Thanks @lyda I sometimes do sign my tags but I don't know the magic incantation to sign pypi releases (tips appreciated). In any case...

$ python setup.py register
running register
running check
Registering mockfs to http://pypi.python.org/pypi
Server response (200): OK

https://pypi.python.org/pypi/mockfs

@davvid davvid closed this Mar 23, 2013
Contributor
zyga commented Mar 24, 2013

Add this to your setup.cfg:

[upload]
sign=True

Collaborator
davvid commented Mar 24, 2013

awesome. I decided to RTFM and then did

python setup.py sdist upload

...and it signed it this time. very nice, thank you.

pyfakefs is also available on pypi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment