Hey pylones -

Myghty will have a new release soon featuring a rewrite of its  
internal buffering methodology, introducing comprehensive character  
encoding support.  This version will allow templates to specify any  
encoding, independently of component output encoding which can be  
specified at the interpreter, request, or programmatic level.   
Multiple component encodings can also be mixed, where they will all  
be decoded to unicode internally and encoded back out consistently.  
The behavior of encoding/decoding errors is also configurable at the  
interpreter, request, or programmatic level.  and of course, you can  
stick a unicode object into m.write() without issue.

I was hoping that some folks could try out the SVN branch ahead of  
time, to help insure that a release can go straight into existing  
Pylons applications with no issues.   There are no incompatible API  
changes, and It should be a drop-in replacement....the Myghty site is  
running it now.   We've also optimized the refactoring as much as  
possible so that it introduces only a very slight additional  
processing overhead, so performance should be comparable...and those  
of you who have extra unicode-compatibility hacks worked into your  
Pylons applications should be able to remove them with this version.

Information on the branch, including a README,  is available at:

http://www.myghty.org/unicode.myt

svn checkout available at:

svn co http://svn.myghty.org/myghty/branches/unicode-opt2/

Please email the myghty list or post trac tickets on the myghty site  
(http://www.myghty.org/trac/) if you have issues.

And thanks very much to Jeff Dairiki for his efforts in producing a  
ton of terrific architecture and code for this task.

- mike

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to