[chirp_users] Trouble getting started

[Sam J]

Thanks.  I installed Python 2.7.3 from source, this afternoon.  It said it 
compiled OK, although it warned of a handful of modules that didn't compile.

Chirp complained it couldn't fine gtk.  I want to spend some time looking at 
the fresh python install before I bug you guys too much.

-sj


=====================================================
On Sunday 09 December 2012 03:52:30 pm David Ranch wrote:
> It's worth noting that you CAN localize newer installations of Python
> say, /usr/local/python2.7 and leave your regular distro's Python alone.
> When you want to run Chirp, you'll just need to start it via your
> desired python like:
>
>     /usr/local/python2.7/python /path/to/chirp/chirp.py
>
> I had to do this on Centos5 and it worked well.
>
> --David
>
> On 12/08/2012 05:37 PM, Dan Smith wrote:
> >> Try upgrading to Python 2.6 or 2.7.
> >
> > Yeah, 2.5 is really old at this point and lacks some of the now-basic
> > features of python that Chirp requires. Note that this likely means a
> > distro upgrade. Installing python from source or other packages is
> > likely to turn into a large string of dependency-chasing exercises that
> > you probably don't want to start.
> >
> >
> >
> > _______________________________________________
> > chirp_users mailing list
> > chirp_users at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20121209/deff7901/attachment.bin