Hey hey,
A quick heads up. David Boddie has created a package that solves this
problem (he emailed me about it this morning).
Great to see the community step up like this. There's still lots of ways
you can get involved with RaspberryPi.
:-)
N.
On 27/03/15 17:44, Steve Holden wrote:
> Excellen
Excellent research! Doubt I'm going to be helping wit this but very much behind
it. S
On Mar 27, 2015, at 10:02 AM, René Dudfield wrote:
> Ok, here's a start... I gathered more information, and found an
> alternative[0].
>
>
> Seems i2c-tools needs to make a new release first? That would be
Ok, here's a start... I gathered more information, and found an
alternative[0].
Seems i2c-tools needs to make a new release first? That would be the place
to ask first. http://www.lm-sensors.org/browser/i2c-tools/trunk
Then the Debian package can be updated:
https://packages.debian.org/wheez
On 24 March 2015 at 21:50, Andrew Farrell wrote:
> Hi Steve,
>
> That is in fact what I was planning on doing. I ought to have disclosed
> that I actually work for Continuum Analytics, though I'd probably be trying
> this out as just as a personal weekend project.
> I'll also be trying this on QE
Ah ha!
from the 2nd link:
# Python 2 and 3: option 1from six import reraise as raise_# orfrom
future.utils import raise_
traceback = sys.exc_info()[2]raise_(ValueError, "dodgy value", traceback)
Perfect, thanks Tim.
On Fri, Mar 27, 2015 at 10:54 AM, Tim Golden wrote:
> On 27/03/2015 10:47, Ha
On 27/03/2015 10:47, Hansel Dunlop wrote:
> Happy Friday Python People! (yes, you're happy, because it's Friday)
>
> Two questions for you:
>
> 1. I'm releasing a library. That I wrote in 2.7. But I want it to make it
> compatible with 2.7+. What's the best approach for this? Especially
>
Happy Friday Python People! (yes, you're happy, because it's Friday)
Two questions for you:
1. I'm releasing a library. That I wrote in 2.7. But I want it to make it
compatible with 2.7+. What's the best approach for this? Especially
when a bit of code for 2.7 is a SyntaxError in 3+
