[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Removing '.py' from system path installed Python

From: Greg Troxel
Subject: Re: [Discuss-gnuradio] Removing '.py' from system path installed Python scripts
Date: Fri, 19 Oct 2007 13:57:15 -0400
User-agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (berkeley-unix)

Frank Brickle <address@hidden> writes:

>> Given that new versions of python can be installed and made default
>> (meaning invoked as 'python'), it's necessary to bind the scripts to the
>> same version of python used to build .so modules and install .py files
>> in site-packages...
> I'm curious -- really just curious -- why not create a chroot
> environment for gnuradio? Or, where the kernel and the CPU allow,
> a fully virtualized stable OS install simply for gnuradio?

You could, but a chroot per package would lead to a vast number of
chroots, and it wouldn't solve the underlying problem of maintaining

If one views the computer's sole purpose as providing a way to run Gnu
Radio, that might be reasonable.  If one views GNU Radio as one of many
components in an overall system - for instance providing the low-level
network connectivity, then it isn't reasonable.

The lack of python binding really is just plain suboptimal (or wrong) -
but becaues most people rarely change python bindings, and because GNU
Radio hackers constantly rebuild/reinstall GNU Radio, it hardly ever
causes trouble.

I don't expect other people to fix this if they don't want to spend the
effort.  pkgsrc currently works around this by having a list of files in
which the interpreter is changed as they are installed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]