Skip to content
This repository was archived by the owner on Jul 30, 2024. It is now read-only.
This repository was archived by the owner on Jul 30, 2024. It is now read-only.

Submit 2.0 to PyPI #9

Open
Open

Description

@JohnDoee

Can you submit 2.0 to PyPI ? seems like 1.1 is the latest: https://pypi.python.org/pypi/pybloom

Activity

  1. jaybaird commented on Apr 10, 2013

    @jaybaird
    Owner

    I'll try to get to this this week. It was submitted to PyPI under an email I no longer have control of, so it may take me a while.

  2. bgilbert commented on May 16, 2014

    @bgilbert

    Any news on this? It's sort of painful to have to use dependency_links in setup.py to declare a dependency on current pybloom, and pip 1.6 is apparently going to drop support for dependency_links altogether.

  3. Bachmann1234 commented on Jun 10, 2014

    @Bachmann1234
    Contributor

    @jaybaird i'd be down for an update on this a well. I am interested in putting some work into this library if you are still able to maintain it.

  4. JohnDoee commented on Jun 10, 2014

    @JohnDoee
    Author

    I think someone needs to take the baton, try and get in touch with @jaybaird and take over management of the project (PyPi stuff etc). It would be sad to see it die just because the current owner lost interest / time / whatever.

    Judging by his twitter, he isn't internet-dead.

  5. Bachmann1234 commented on Jun 10, 2014

    @Bachmann1234
    Contributor

    hmmm, ill reach out

  6. Bachmann1234 commented on Jun 10, 2014

    @Bachmann1234
    Contributor

    @JohnDoee just sent @jaybaird an email offering to adopt this project.

  7. jaybaird commented on Jun 10, 2014

    @jaybaird
    Owner

    Nope, not dead, just working at Apple :)

    The PyPI thing is hard because I have no way of getting control of that package since it was submitted under my old work email. If you folks know of a way to get control of that again I'm all ears so I can submit.

  8. JohnDoee commented on Jun 10, 2014

    @JohnDoee
    Author

    Good to see you alive and kicking :)

    You can get your email changed by submitting a ticket here: http://sourceforge.net/p/pypi/support-requests/ at least, that's what other folks did.

  9. jaybaird commented on Jun 10, 2014

    @jaybaird
    Owner

    Awesome, thanks mate. I'll get that in right now.

  10. bgilbert commented on Jun 16, 2014

    @bgilbert

    @jaybaird Any luck? For some reason, I'm not seeing your ticket on the PyPI support board.

  11. jaybaird commented on Jun 16, 2014

    @jaybaird
    Owner

    I had a busy weekend and had to get my SourceForge credentials back up to date as well. It’s on my to do list this week though.

    Jay

    On Jun 16, 2014, at 12:45 PM, Benjamin Gilbert notifications@github.com wrote:

    @jaybaird Any luck? For some reason, I'm not seeing your ticket on the PyPI support board.

    —
    Reply to this email directly or view it on GitHub.

  12. Bachmann1234 commented on Jun 28, 2014

    @Bachmann1234
    Contributor

    @jaybaird any update? Anything we can do to help?

  13. hosford42 commented on May 28, 2015

    @hosford42

    @jaybaird Any word on this? I'm having the same issue... If there is no way to get access to the original account, could you republish under a new package name?

  14. jhgg commented on Jun 15, 2015

    @jhgg

    +1

  15. mdshw5 commented on Jul 29, 2015

    @mdshw5

    Yes, maybe this can be resubmitted under a new name? It's kind of silly that the PyPI version is so far behind the current master...

  16. JohnDoee commented on Aug 3, 2015

    @JohnDoee
    Author

    Another issue is that it seems like jaybaird isn't very active here anymore.

    My solution is that we should move it all to a fork and run the project there.

    I elect myself to do all this, not because I'm the best choice but because someone has to put up their hand to get things moving.

    Feel free to volunteer yourself to handle it or throw in some critique / comments. I'll give it a few weeks and just do it if nothing new appears.

  17. hosford42 commented on Aug 3, 2015

    @hosford42

    I considered doing that myself, but I didn't know if it would be polite. I am for it as well, if we don't get a response from him in that time frame. (It has been over a year since he was last seen here, after all.) If you need any assistance packaging, testing, or posting it, let me know.

  18. jhgg commented on Aug 3, 2015

    @jhgg

    Honestly, if you are going to fork this, I'd recommend redoing the hash stuff too. Using cryptographically secure hashes in a bloomfilter is pointless & slows things down. Should be using murmur3 hash instead.

  19. jhgg commented on Aug 3, 2015

    @jhgg

    I wrote https://github.com/jhgg/pybloof using the faster hashing algorithm. But I think it needs some review & API improvements.

  20. bgilbert commented on Aug 4, 2015

    @bgilbert

    PyPI's draft transfer policy allows PyPI packages to be transferred by a PyPI admin with permission from the current owner. If @jaybaird would be willing to give his permission, development could continue under the current PyPI package name (and presumably a different GitHub account). If not, I think forking makes sense.

  21. RazerM commented on Oct 21, 2015

    @RazerM

    I think I'll be submitting this to PyPI with a slightly different name, if only because I can't find any other implementations of a bloom filter that support Python 3 and/or Windows (which I plan on building wheels for using AppVeyor).

    I'd also be happy to conribute the AppVeyor stuff if someone else would prefer to fork (@JohnDoee, @hosford42)

    Edit: I looked at so many different bloom filters I forgot this one is pure Python, only need to upload...

  22. nirizr commented on Jun 30, 2016

    @nirizr

    Looks like this fork is trying to reanimate this module

  23. joseph-fox commented on Jun 30, 2016

    @joseph-fox

    @nirizr Yes, I have been trying my best to keep the forked repository active.

    It is available in pypi.

  24. nirizr commented on Jun 30, 2016

    @nirizr

    Yep. Just wanted to make it more visible :)

  25. added a commit that references this issue on Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions