Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Drak
Yes. I think the problem is your fork has been under more development and upstream has stalled. The problem with this is it becomes unclear which repo is the main one as it really has become a fork and of course then development really does fork properly which is a shame because it doesn't nurture

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Drak
Would it make sense to pull that stuff in and add Peter with commit access since your repo is top of the fork tree. Drak On 15 March 2014 16:47, Jeff Garzik wrote: > Sounds great. I'm glad to see this with a more active maintainer. > Maintaining -three- client libs was a bit much for me. > >

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Peter Todd
On Sat, Mar 15, 2014 at 05:12:42PM +, Drak wrote: > Would it make sense to pull that stuff in and add Peter with commit access > since your repo is top of the fork tree. I've noticed it looks like people actually using my 'pythonize' code have been linking directly to my tree in things like do

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Jeff Garzik
I am happy to do whatever makes the new maintainer and users most happy. That includes giving the new maintainer commit privs in my repo. On Sat, Mar 15, 2014 at 1:12 PM, Drak wrote: > Would it make sense to pull that stuff in and add Peter with commit access > since your repo is top of the for

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Jeff Garzik
Sounds great. I'm glad to see this with a more active maintainer. Maintaining -three- client libs was a bit much for me. On Sat, Mar 15, 2014 at 9:43 AM, Peter Todd wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I noticed that the ngccbase Colored Coin client(1) added a > python-

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Jeff Garzik
Thanks -- though credit is really due to ArtForz, who kicked off this project with his half-a-node: http://pastebin.com/ZSM7iHZw On Sat, Mar 15, 2014 at 10:34 AM, Peter Todd wrote: > On Sat, Mar 15, 2014 at 09:43:40AM -0400, Peter Todd wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256

Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Peter Todd
On Sat, Mar 15, 2014 at 09:43:40AM -0400, Peter Todd wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I noticed that the ngccbase Colored Coin client(1) added a > python-bitcoinlib dependency, specifically my fork. In addition there is > also now a rudementary python-bitcoinlib packa

[Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol

2014-03-15 Thread Peter Todd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I noticed that the ngccbase Colored Coin client(1) added a python-bitcoinlib dependency, specifically my fork. In addition there is also now a rudementary python-bitcoinlib package in archlinux. So with that in mind I'm releasing v0.1, perhaps somew