Re: [cedar-backup-users] Resultc from python util/test.py (Ubutnu Jaunty 9.04)

[Kenneth P. <pro...@ie...>]

It should be safe to install multiple pythons alongside one another.  You're
not rolling back, because the default system interpreter will remain at
2.6.  Basically, the existing /usr/bin/python will continue to point at
/usr/bin/python2.6, but the new /usr/bin/python2.5 will also be available if
you want to use it.  (My Debian lenny box has both 2.4 and 2.5 installed,
using the same mechanism.)

KEN

On Mon, May 4, 2009 at 3:47 PM, Scott Evans <sc...@vk...>wrote:

>
> No doubt that there has been internal changes with Python 2.6 but I too am
> not too concerned about the depreciation warnings!
>
> As for rolling back to Pyton  2.5 this will possibly break Jaunty! as some
> applications rely on that newer release! (I don't want that!)
>
> For one backup I also discovered that I had a faulty DVD/RW that just also
> added some confusion as to what was at fault! (time to get some new media!)
>
>
> -----Original Message-----
> *From*: Kenneth Pronovici <pro...@ie...<Kenneth%20Pronovici%20%3cp...@ie...%3e>
> >
> *To*: cedar-backup-users <ced...@li...<cedar-backup-users%20%3cc...@li...%3e>
> >
> *Subject*: Re: [cedar-backup-users] Resultc from python util/test.py
> (Ubutnu Jaunty 9.04)
> *Date*: Mon, 4 May 2009 14:27:47 -0500
>
> Just to follow up briefly: Python 2.6 is currently only available in
> Debian's experimental distribution.  I could install it from source, but I
> would prefer not to.  So, I will address these test failures at some point
> in the future when I can more easily install the new interpreter.
>
> In the meantime, if you are concerned, you could install Ubuntu's python2.5
> package, and then change the cback script to use this:
>
> #!/usr/bin/python2.5
>
> I wouldn't worry about it, though.
>
> KEN
>
> On Mon, May 4, 2009 at 7:56 AM, Kenneth Pronovici <pro...@ie...>
> wrote:
>
> Hi Scott,
>
> Thanks for the report.
>
> I haven't tested with Python 2.6 previously, and it looks like that
> explains most of the DeprecationWarning items you see.  Deprecations
> should be harmless (for now) so these are nothing to worry about.
>
> I'll take a look at testGenerateTarfile_002(); as you might surmise
> from the comment, Python 2.5 behavior differs from 2.4 and 2.3, so
> perhaps 2.6 changed again.  I recall this being a test-only issue the
> last time (something to do with how I detect the expected results), so
> again I don't think it's anything to worry about.
>
> I'll reply again once I've had a chance to look at things in detail.
>
> KEN
>
>