Re: [myhdl-list] attribute enum_encoding: string;

[Christopher F. <chr...@gm...>]

On 9/5/2013 6:20 AM, Angel Ezquerra wrote:
> My point was that perhaps calling MyHDL enums "enum" which is a
> builtin type in Python 3.4 (I believe!) may cause trouble long term,
> since it may require having to modify existing MyHDL files.
>
> Cheers,
>
> Angel
>

I am sure there are other projects that will have
to deal with the /enum/ collision(?).  I don't think
we would want to discourage the use of the myhdl.enum.

It shouldn't be an issue with existing or developing code,
it is assumed they are not using the py3.enum, the myhdl.enum
will be in the namespace.  The only issue would be if
someone wanted to update old code with py3.enum in the future,
I think is highly unlikely.

Regards,
Chris

> On Thu, Sep 5, 2013 at 1:06 PM, Christopher Felton
> <chr...@gm...> wrote:
>> On 9/4/13 11:49 PM, Angel Ezquerra wrote:
>>> Chris,
>>>
>>> I have not followed this in much detail so please excuse me if this is
>>> obvious: Is this "enum" a MyHDL class? I ask because Python 3 will get
>>> a builtin enum class. I think we should make sure that we make it
>>> possible to use it if MyHDL is ever ported to Python 3.
>>>
>>> Cheers,
>>>
>>> Angel
>>>
>>>
>>
>> Yes, the "enum" is from the MyHDL package.  Something might
>> need to be done to be compatible with the latest version of
>> Python 3 when we get there :)
>>
>> Regards,
>> Chris
>>
>>