Submit 2.0 to PyPI about python-bloomfilter HOT 24 OPEN

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

It is available in pypi.

from python-bloomfilter.

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.

from python-bloomfilter.

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.

from python-bloomfilter.

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.

from python-bloomfilter.

@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.

from python-bloomfilter.

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.

from python-bloomfilter.

hmmm, ill reach out

from python-bloomfilter.

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

from python-bloomfilter.

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.

from python-bloomfilter.

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.

from python-bloomfilter.

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

from python-bloomfilter.

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

from python-bloomfilter.

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 [email protected] 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.

from python-bloomfilter.

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

from python-bloomfilter.

@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?

from python-bloomfilter.

+1

from python-bloomfilter.

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...

from python-bloomfilter.

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.

from python-bloomfilter.

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.

from python-bloomfilter.

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

from python-bloomfilter.

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.

from python-bloomfilter.

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...

from python-bloomfilter.

Looks like this fork is trying to reanimate this module

from python-bloomfilter.

Yep. Just wanted to make it more visible :)

from python-bloomfilter.