Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WOsVX-0007hj-KF for bitcoin-development@lists.sourceforge.net; Sat, 15 Mar 2014 17:36:27 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of zikula.org designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; envelope-from=drak@zikula.org; helo=mail-wg0-f41.google.com; Received: from mail-wg0-f41.google.com ([74.125.82.41]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WOsVW-0008I7-9g for bitcoin-development@lists.sourceforge.net; Sat, 15 Mar 2014 17:36:27 +0000 Received: by mail-wg0-f41.google.com with SMTP id n12so3194741wgh.0 for ; Sat, 15 Mar 2014 10:36:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7f8bq0iRt6/xPBM1buQHAUTSLkrhp4Og6U7R5NuZ47Y=; b=HXzx7yPtJdNiMmlk0Cx1+zAKA3lDo5Lp7ZSqiraVb4EqZ50mf4RD5+sCFy+KVSnfHx T0vGC2ZBhMDeABAPqxFZVkb3c709cMjngSxKbvh2c+8natiqYk+m+kTPpylqv1EeCKyQ 1kF1RwhWoEf8XSBaI2XzFtf4zVzmHq6YSwFZkLTkA1B8b/yhYh+LBv7ijTxg5jdbKFSM bkpxNYlf9ObHj6w2douq7WZCYg7m4kBrTFnZI+l8HVHJs5CBCQBySkTIsvvL7rwmLZdP 1lBGhERsCitmzpsqD39hz4evy+ZYH6IUAmPM/5FcX9CmHO9urxjRf/VgtkNL6dsX8x1N MgfQ== X-Gm-Message-State: ALoCoQkurZ99w58lu2GDCzwJIxKtvd75phP3aIYjQd0oHtAek8YqzK4Y6ti6cFgNLuNS68/SJl1E X-Received: by 10.180.185.197 with SMTP id fe5mr3028011wic.56.1394903583024; Sat, 15 Mar 2014 10:13:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.205.69 with HTTP; Sat, 15 Mar 2014 10:12:42 -0700 (PDT) In-Reply-To: References: <20140315134340.GA12937@savin> From: Drak Date: Sat, 15 Mar 2014 17:12:42 +0000 Message-ID: To: Jeff Garzik Content-Type: multipart/alternative; boundary=001a11c34e9e8fffb504f4a84ced X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WOsVW-0008I7-9g Cc: Bitcoin Dev , Andy Weidenbaum , Alex Mizrahi Subject: Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2014 17:36:27 -0000 --001a11c34e9e8fffb504f4a84ced Content-Type: text/plain; charset=UTF-8 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. > > 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-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 somewhat arbitrarily: > > > > https://github.com/petertodd/python-bitcoinlib/tree/v0.1 > > > > This Python2/3 library provides an easy interface to the bitcoin data > > structures and protocol. The approach is low-level and "ground up", with > > a focus on providing tools to manipulate the internals of how Bitcoin > > works in a Pythonic way, without straying far from the Bitcoin Core > > implementation. > > > > The current status of the library as of v0.1 is that the support for > > data-structures related to transactions, scripting, addresses, and keys > > are all quite usable and the API is probably not going to change that > > much. Bitcoin Core RPC support is included and automatically converts > > the JSON to/from Python objects when appropriate. EvalScript(), > > VerifyScript(), and SignatureHash() are all functional and pass all the > > Bitcoin Core unittests, as well as a few that are still yet to be > > merged.(2) You'll find some examples for signing pay2script-hash and > > p2sh txouts in the examples/ directory; I personally used the > > transaction signing functionality to make up a set of unittests related > > to OP_CODESEPARATOR and FindAndDelete() recently. Finally my dust-b-gone > > script(3) is another good example, specifically of the RPC > > functionality. > > > > I personally haven't had any need for the p2p network related code for > > some time, so I'm sure it's not in a good state and it lacks unittests; > > Bloom filters for one are missing the merkle-block support to actually > > make them useful. But the RPC support makes up for that for many uses. > > > > This release and others in the future are signed by my PGP key, as well > > as every publicly pushed commit. You can verify the key via WoT, my > > bitcointalk account, signing history in the Bitcoin Core repo, and > > mailing list records among other sources. > > > > Disclaimer: This is alpha code in a language not known for type-safety. > > I wouldn't personally use python-bitcoinlib for anything > > other than experiments and neither should you. > > > > 1) https://github.com/bitcoinx/ngcccbase > > 2) https://github.com/bitcoin/bitcoin/pull/3861 > > 3) https://github.com/petertodd/dust-b-gone > > > > - -- > > 'peter'[:-1]@petertodd.org > > 000000000000000097649e8d66395b3cb4527263409adf628c76cc56af0434fe > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.14 (GNU/Linux) > > > > iQGrBAEBCACVBQJTJFkFXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw > > MDAwMDAwMDAwMDAwMDA3OGEyNGUxNTBlNTc2ZGVjZWUyYWQzMGNhMmE2YTRhMmM3 > > NGVkYmJkNjM2NDViNjcvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 > > ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftZiwgAk8YVN9t76tKIKcWKyrGgv8yk > > UZGZkkrowED0lyhMXfmviezeWhjvHZgQrwha2hAuik36WEBN1jnv9wuJ6g9tnxGY > > PyG8n1SV2rtQ/QIJyL6wOuqL3UZi6d6IdZ/udVmyGwz+XhE89AwitR0++MvxkPNv > > i9R3Gw5Z1CnS2W0jGpAT88k3q3pqEzbYutP/FaylL2+6MuSUGwHUoY8dqcRkwkw1 > > eIrd2W33x4NvuxYPLnHR64uE0B8KoreZOyyskMdeMsKtZNflkfgfMiD10xnw2PGx > > z8S42wPbrI5ZYLL1OLdRfuKMdQ4qOyF4jfV+QRZWQ5t5Qh1akVWmz7ffFHGo0Q== > > =k1pi > > -----END PGP SIGNATURE----- > > > > -- > Jeff Garzik > Bitcoin core developer and open source evangelist > BitPay, Inc. https://bitpay.com/ > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --001a11c34e9e8fffb504f4a84ced Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Would it make sense to pull that stuff in and add Peter wi= th commit access since your repo is top of the fork tree.

Drak


On 15 = March 2014 16:47, Jeff Garzik <jgarzik@bitpay.com> wrote:
Sounds great. =C2=A0I'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 <pete@petertodd.org> 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 package in archlinux.
>
> So with that in mind I'm releasing v0.1, perhaps somewhat arbitrar= ily:
>
> =C2=A0 =C2=A0 https://github.com/petertodd/python-bitcoinl= ib/tree/v0.1
>
> This Python2/3 library provides an easy interface to the bitcoin data<= br> > structures and protocol. The approach is low-level and "ground up= ", with
> a focus on providing tools to manipulate the internals of how Bitcoin<= br> > works in a Pythonic way, without straying far from the Bitcoin Core > implementation.
>
> The current status of the library as of v0.1 is that the support for > data-structures related to transactions, scripting, addresses, and key= s
> are all quite usable and the API is probably not going to change that<= br> > much. Bitcoin Core RPC support is included and automatically converts<= br> > the JSON to/from Python objects when appropriate. =C2=A0EvalScript(),<= br> > VerifyScript(), and SignatureHash() are all functional and pass all th= e
> Bitcoin Core unittests, as well as a few that are still yet to be
> merged.(2) You'll find some examples for signing pay2script-hash a= nd
> p2sh txouts in the examples/ directory; I personally used the
> transaction signing functionality to make up a set of unittests relate= d
> to OP_CODESEPARATOR and FindAndDelete() recently. Finally my dust-b-go= ne
> script(3) is another good example, specifically of the RPC
> functionality.
>
> I personally haven't had any need for the p2p network related code= for
> some time, so I'm sure it's not in a good state and it lacks u= nittests;
> Bloom filters for one are missing the merkle-block support to actually=
> make them useful. But the RPC support makes up for that for many uses.=
>
> This release and others in the future are signed by my PGP key, as wel= l
> as every publicly pushed commit. You can verify the key via WoT, my > bitcointalk account, signing history in the Bitcoin Core repo, and
> mailing list records among other sources.
>
> Disclaimer: This is alpha code in a language not known for type-safety= .
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I wouldn't personally us= e python-bitcoinlib for anything
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 other than experiments and n= either should you.
>
> 1) https://github.com/bitcoinx/ngcccbase
> 2) https://github.com/bitcoin/bitcoin/pull/3861
> 3) https://github.com/petertodd/dust-b-gone
>
> - --
> 'peter'[:-1]@petertodd.org
> 000000000000000097649e8d66395b3cb4527263409adf628c76cc56af0434fe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
>
> iQGrBAEBCACVBQJTJFkFXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
> MDAwMDAwMDAwMDAwMDA3OGEyNGUxNTBlNTc2ZGVjZWUyYWQzMGNhMmE2YTRhMmM3
> NGVkYmJkNjM2NDViNjcvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
> ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftZiwgAk8YVN9t76tKIKcWKyrGgv8yk
> UZGZkkrowED0lyhMXfmviezeWhjvHZgQrwha2hAuik36WEBN1jnv9wuJ6g9tnxGY
> PyG8n1SV2rtQ/QIJyL6wOuqL3UZi6d6IdZ/udVmyGwz+XhE89AwitR0++MvxkPNv
> i9R3Gw5Z1CnS2W0jGpAT88k3q3pqEzbYutP/FaylL2+6MuSUGwHUoY8dqcRkwkw1
> eIrd2W33x4NvuxYPLnHR64uE0B8KoreZOyyskMdeMsKtZNflkfgfMiD10xnw2PGx
> z8S42wPbrI5ZYLL1OLdRfuKMdQ4qOyF4jfV+QRZWQ5t5Qh1akVWmz7ffFHGo0Q=3D=3D > =3Dk1pi
> -----END PGP SIGNATURE-----



--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0https://bitpay.com/

-----------------------------= -------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases = and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf= .net/sfu/13534_NeoTech
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a11c34e9e8fffb504f4a84ced--