That doesn't work in CPython either...
Python 2.4.1 (#1, May 27 2005, 18:02:40)
[GCC 3.3.3 (cygwin special)] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from xml import *
>>> dir()
['__builtins__', '__doc__', '__name__', 'dom', 'parsers', 'sax']
>>> from sa
Do they have a list up somewhere of what's accepted for 2.5? I looked on
the PEP page and there is no 2.5 release schedule up.
Monty
> We already have generators, but yes. for 1.0 we are tragetting 2.4
> compatibility (I may even implement few of the 2.5 upcoming features such
> as the new 'with'
Static compilation is a big ticket item for me. I'm doing work for a shop
that has a .NET-driven reporting package that is a replacement for an
older collection of scripts. Some of them are Python, which I would like
to see more of, but we have to shell out to them. A co-worker tried to
rewrite the
Could you use the CPython mechanisms for new language features, i.e.:
from __future__ import generics
> I think this raises the question of how to best flag a script as requiring
> a certain set of features (generics, 32 vs 64 bit assemblies, etc).
>
> ___
Hi Brian,
Would you consider Python for .NET ready enough to use as a conduit
between Zope and .NET in a production environment? I'm currently working
on a Zope app that lives in a .NET world and I think this would help me
stem the tide of people who want to rewrite it in C#.
Thanks!
Monty
__
