You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 30, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 30, 2024. It is now read-only.
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.
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.
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.
@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?
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.
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.
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.
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...
Activity
jaybaird commentedon Apr 10, 2013
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.
bgilbert commentedon May 16, 2014
Any news on this? It's sort of painful to have to use
dependency_linksinsetup.pyto declare a dependency on current pybloom, and pip 1.6 is apparently going to drop support fordependency_linksaltogether.Bachmann1234 commentedon Jun 10, 2014
@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.
JohnDoee commentedon Jun 10, 2014
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.
Bachmann1234 commentedon Jun 10, 2014
hmmm, ill reach out
Bachmann1234 commentedon Jun 10, 2014
@JohnDoee just sent @jaybaird an email offering to adopt this project.
jaybaird commentedon Jun 10, 2014
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.
JohnDoee commentedon Jun 10, 2014
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.
jaybaird commentedon Jun 10, 2014
Awesome, thanks mate. I'll get that in right now.
bgilbert commentedon Jun 16, 2014
@jaybaird Any luck? For some reason, I'm not seeing your ticket on the PyPI support board.
jaybaird commentedon Jun 16, 2014
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
Bachmann1234 commentedon Jun 28, 2014
@jaybaird any update? Anything we can do to help?
hosford42 commentedon May 28, 2015
@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?
jhgg commentedon Jun 15, 2015
+1
mdshw5 commentedon Jul 29, 2015
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...
JohnDoee commentedon Aug 3, 2015
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.
hosford42 commentedon Aug 3, 2015
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.
jhgg commentedon Aug 3, 2015
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.
jhgg commentedon Aug 3, 2015
I wrote https://github.com/jhgg/pybloof using the faster hashing algorithm. But I think it needs some review & API improvements.
bgilbert commentedon Aug 4, 2015
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.
RazerM commentedon Oct 21, 2015
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...
nirizr commentedon Jun 30, 2016
Looks like this fork is trying to reanimate this module
joseph-fox commentedon Jun 30, 2016
@nirizr Yes, I have been trying my best to keep the forked repository active.
It is available in pypi.
nirizr commentedon Jun 30, 2016
Yep. Just wanted to make it more visible :)
Merge pull request jaybaird#9 from joseph-fox/hotfix/space-issue