myhdl-list

[myhdl-list] installing myhdl stable and development package in parallel

[Günter D. <dan...@we...>]

Hello,

Has somebody figured out a good way to install the stable version and 
the code from the repository in parallel without the packages 
interfering with each other?

I did check out the mercurial code as myhdl_hg and then set the 
PYTHONPATH to it. My idea was to decide by the way of doing the import 
to take either of the packages. So instead of doing 'from myhdl' do 
'from myhdl_hg.myhdl'. Unfortunately there are imports inside the myhdl 
package that do the 'from myhdl' type import. So I end up mixing 
packages when doing the import from the repository.

Are there any better ways of doing that?

Cheers,

Guenter

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Christopher L. F. <pu...@gm...>]

> Are there any better ways of doing that?

I don't know if this is better or has the same issue but what I have  
been doing is similar, I cloned from the repository to something say  
myhdl_hg.

Then in the directory of my current myhdl WIP I create a soft link (ln  
-s) to myhdl_hg.  When I do an import myhdl it will grab from the  
local directory.  When I want to go back to the release version I  
remove the link.

You could also do this by removing the directory in site-packages and  
adding a soft link there.

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Thomas T. <tho...@de...>]

> Has somebody figured out a good way to install the stable version and 
> the code from the repository in parallel without the packages 
> interfering with each other?

I did the following. I am not sure, whether it really avoids intermixing
- but it should.

import sys
sys.path.insert(0,"path_to_myhdl_hg")
....

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Jan D. <ja...@ja...>]

Günter Dannoritzer wrote:
> Hello,
> 
> Has somebody figured out a good way to install the stable version and 
> the code from the repository in parallel without the packages 
> interfering with each other?
> 
> I did check out the mercurial code as myhdl_hg and then set the 
> PYTHONPATH to it. My idea was to decide by the way of doing the import 
> to take either of the packages. So instead of doing 'from myhdl' do 
> 'from myhdl_hg.myhdl'. Unfortunately there are imports inside the myhdl 
> package that do the 'from myhdl' type import. So I end up mixing 
> packages when doing the import from the repository.
> 
> Are there any better ways of doing that?

I wouldn't try to use the python namespace to control version selection.

I think the cleanest way is to control $PYTHONPATH. Suppose the stable
version is selected by default, then you could have a shell script
to select the development version instead, by doing something like:

PYTHONPATH="$HOME/dev/myhdl:${PYTHONPATH}"
export PYTHONPATH


-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Günter D. <dan...@we...>]

Jan Decaluwe wrote:

> 
> PYTHONPATH="$HOME/dev/myhdl:${PYTHONPATH}"
> export PYTHONPATH
> 
> 

Thanks to all the replies. They helped me to figure out a better way to 
do it.

I decided to go with the script way as proposed by Jan. Putting it into 
a central place I can source it from the current shell and by that use 
the development snapshot in the current shell.

Cheers,

Guenter

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Brendan <bre...@gm...>]

Günter Dannoritzer <dannoritzer@...> writes:

> I decided to go with the script way as proposed by Jan. Putting it into 
> a central place I can source it from the current shell and by that use 
> the development snapshot in the current shell.
> 
> Cheers,
> 
> Guenter
> 

You could also use Ian Bicking's excellent virtualenv.  It's especially handy
for determining how you would deploy customized Python on production machines.

- Brendan