Re: [myhdl-list] Further development setup

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

Jan Decaluwe wrote:
...
> 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.

When I read the explanation about the compiler package at this page:

http://docs.python.org/library/compiler.html

It talks about that the compiler converts the Python code to an abstract
syntax tree and from there creates the Python bytecode.

Unfortunately I have not understood that process much deeper yet, but if
I recall it right, then the MyHDL converter uses the abstract syntax
tree to create the Verilog or VHDL code from. So the last step, the
Python bytecode is not really needed.

This makes me think whether it would make sense to take the compiler
package as part of myhdl? At least the part that parses Python code and
create the abstract syntax tree. This would ease the requirement to
change the conversion software in the time line of Python 2.6.

Guenter