[myhdl-list] Further development setup

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

It's time to set things up for new developments. There
are a number of issues that I'd like to describe.

Python 2.6
----------
I plan to move to Python 2.6. It's becoming the "sweet spot"
now and it's a necessary step to prepare for Python 3.0.

MyHDL 0.7
---------
Unfortunately, we're having a kind of a setback. The
conversion software was written using the "compiler" package.
This is deprecated in 2.6 and removed in 3.0. Instead,
the new package to use is "ast". This has the advantage
that it's closely related to the Python parser, but unfortunately
it requires a complete rewrite of the conversion code.

I have no idea how complicated this is going to be. I have
the tests, and an existing implementation of course, but
I don't expect it to be trivial.

Also, I'm not very motivated to support new things in the
convertor before the rewrite is done.

Mercurial named branches
------------------------
I plan to use named branches for the first time in mercurial,
to support simultaneous maintenance of 0.6 and further
development on the trunk. I believe this will be easier
for me than separate repositories.

It means that if you track the repository, you will have
to make sure to switch to the correct branch depending
on what you want to track.

More about this when it actually starts happening.


Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
    Python as a HDL: http://www.myhdl.org
    VHDL development, the modern way: http://www.sigasi.com
    Analog design automation: http://www.mephisto-da.com
    World-class digital design: http://www.easics.com