Amara 2 and Python 3.3

[Werner]

Hi everyone,

Over the next few month I am planning to start testing/evaluating/moving
my shareware stuff to Python 3.3.

What is the status of Amara 2 with regards to Python 3.3?

Is it already compatible with it or if not what are the plans to support it?

Best regards
Werner

[werner]

Hi,

Sorry to be a ....:)

I would really like to start moving my stuff to Python 3.3.

What is the situation with Amara 2 at this point?

Werner

[Luis Miguel Morillas]

2014-04-21 16:15 GMT+02:00 werner <wern...@gmx.ch>:
> Hi,
>
> Sorry to be a ....:)
>

:) Lol

> I would really like to start moving my stuff to Python 3.3.
>
> What is the situation with Amara 2 at this point?
>

Uche wants to work on porting amara to python 3.x , but sure he hasn't
time to do it as soon as he wanted to.

Uche, do you want to write an action plan so others could contribute with you?

--

Luis Miguel

> Werner
>
>
>
> On Thursday, 5 September 2013 11:37:28 UTC+2, werner wrote:
>>
>> Hi everyone,
>>
>> Over the next few month I am planning to start testing/evaluating/moving
>> my shareware stuff to Python 3.3.
>>
>> What is the status of Amara 2 with regards to Python 3.3?
>>
>> Is it already compatible with it or if not what are the plans to support
>> it?
>>
>> Best regards
>> Werner
>

> --
> You received this message because you are subscribed to the Google Groups
> "akara" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akara+un...@googlegroups.com.
> To post to this group, send email to ak...@googlegroups.com.
> Visit this group at http://groups.google.com/group/akara.
> For more options, visit https://groups.google.com/d/optout.

[Uche Ogbuji]

Hi Werner, no you've been patient. Sorry. Yes the idea is to make Amara Python 3 compatible, but in doing so I've decided to eliminate the C portions of the code, which in effect means a rewrite. The idea is that only MicroXML parsing would be supported directly, though general XML would be supported via a pipeline from pyexpat. That way we would eliminate our specialized, full-XML parser which is the thing that makes Amara most expensive to maintain, and is also by far the bit that would be hardest to port to Python 3. So it would be killing 2 birds with one stone: simplifying the code base and supporting Python 3.

The main task is the MicroXML parser, which I've started on, but needs more work than I can offer at this moment.

https://github.com/uogbuji/amara3

MicroXML, unlike full XML is just about simple enough to tackle with a general purpose parser tool, unlike full XML. So far I've been using PLY but have eyed Grako. Luis's idea of a roadmap makes sense but again relies on me to find time to craft it. If anyone wants to help, looking into the MicroXML parser basics would be a great start, and would help energize me to figure out a way to carve out time. I think the bindery tools and such shouldn't be too hard once the basics are in place.

--Uche

--

Uche Ogbuji                                       http://uche.ogbuji.net
Founding Partner, Zepheira                  http://zepheira.com

Author, Ndewo, Colorado                     http://uche.ogbuji.net/ndewo/
Founding editor, Kin Poetry Journal      http://wearekin.org
Editor & Contributor, TNB     http://www.thenervousbreakdown.com/author/uogbuji/
http://copia.ogbuji.net    http://www.linkedin.com/in/ucheogbuji    http://twitter.com/uogbuji

[Sylvain Hellegouarch]

Hi Uche et al.,

Happy to see you guys are still in that game :)

On 23 April 2014 15:22, Uche Ogbuji <uc...@ogbuji.net> wrote:

Hi Werner, no you've been patient. Sorry. Yes the idea is to make Amara Python 3 compatible, but in doing so I've decided to eliminate the C portions of the code, which in effect means a rewrite. The idea is that only MicroXML parsing would be supported directly, though general XML would be supported via a pipeline from pyexpat. That way we would eliminate our specialized, full-XML parser which is the thing that makes Amara most expensive to maintain, and is also by far the bit that would be hardest to port to Python 3. So it would be killing 2 birds with one stone: simplifying the code base and supporting Python 3.

Would that also mean that Amara is officilly dead? By this I mean, would MicroXML support XPath, XSLT, schema...? I'm sorry for the daft question, I had never heard of it until now.

--
- Sylvain
http://www.defuze.org
http://twitter.com/lawouach

[Uche Ogbuji]

Yes it would still support XPath and XSLT, though namespaces would be  addressed via fix-ups. Amara never supported W3C XML Schema, and never would have. A similar level of Schematron support would remain.

[Sylvain Hellegouarch]

On 23 April 2014 16:03, Uche Ogbuji <uc...@ogbuji.net> wrote:

On Wed, Apr 23, 2014 at 7:28 AM, Sylvain Hellegouarch <s...@defuze.org> wrote:

Hi Uche et al.,

Happy to see you guys are still in that game :)

On 23 April 2014 15:22, Uche Ogbuji <uc...@ogbuji.net> wrote:

Hi Werner, no you've been patient. Sorry. Yes the idea is to make Amara Python 3 compatible, but in doing so I've decided to eliminate the C portions of the code, which in effect means a rewrite. The idea is that only MicroXML parsing would be supported directly, though general XML would be supported via a pipeline from pyexpat. That way we would eliminate our specialized, full-XML parser which is the thing that makes Amara most expensive to maintain, and is also by far the bit that would be hardest to port to Python 3. So it would be killing 2 birds with one stone: simplifying the code base and supporting Python 3.

Would that also mean that Amara is officilly dead? By this I mean, would MicroXML support XPath, XSLT, schema...? I'm sorry for the daft question, I had never heard of it until now.

Yes it would still support XPath and XSLT, though namespaces would be  addressed via fix-ups. Amara never supported W3C XML Schema, and never would have. A similar level of Schematron support would remain.

Thanks for the feedback. Sorry for the schema thing, my mind was set on Relax but I was lazy :p 

[Werner]

Hi Uche,

Thanks for the update.

Werner