[tahoe-dev] packaging for Fedora and Debian blocked on C++ issues (was: plans for tahoe-1.3.0 release)

Brian Warner warner-tahoe at allmydata.com
Mon Feb 9 12:37:40 PST 2009

On Mon, 9 Feb 2009 12:46:47 -0700
zooko <zooko at zooko.com> wrote:

> feature 1: defining hexdigest() by attaching an instance of HexEncoder to
> an instance of ArraySink:

> So we could either remove .hexdigest() entirely or rewrite it to not depend
> on the automatic detection of how to attach a HexEncoder to an ArraySink.

Would it be possible to define our own hexdigest() (perhaps even in python)
which calls the internal .digest() and then hex-encodes the result?
hex-encoding shouldn't be too hard.. heck, I bet even *my* rusty C skills
could figure that one out :).

> feature 2: raising exceptions from Crypto++ and catching them in
> pycryptopp.

Is the symbol-comparison used just to identify *which* C++ exception was
raised? Could we simply catch *all* C++ exceptions and report them in the
same fashion, thus avoiding the symbol-comparison? Or catch all C++
exceptions and then examine the result (with string compares) to decide which
sort of Python exception to report?

I'll see if I can get a chance to look at the pycryptopp code and see if
these two approaches are feasible.


> Okay, so if anyone out there wants to contribute a fix to this, that would
> be great! To replicate the problem is very simple: "python ./ setup.py
> build --disable-embedded-cryptopp && python ./setup.py test".

Thanks for the replication instructions.. that will make it much easier to
get started.


More information about the tahoe-dev mailing list