Hello,
Python language reference 3.3.6 deprecates __getslice__. I think it's
okay that UserList.py has it, but sre_parse shouldn't use it, no?
__getslice__ is not implemented in IronPython and this breaks usage of
_sre.py, a pure-Python implementation of _sre, on IronPython:
http://ubique.ch/code
I do a writing and reading file performance test, the
result is that python2.3 is more faster than
ironpython1.0 beta6.
test result of python2.3 :
write & read [5] M time used:
w: average=[1.363979] std.deviation=[0.383529]
max=[1.930142] min=[0.961854]
r: average=[0.68
2006/4/29, smppms2002 <[EMAIL PROTECTED]> wrote:
> some function not implement in cStringIO
For the time being, you can rebuild with
IronPython/Modules/cStringIO.cs removed, and put a stub cStringIO.py
that imports everything from StringIO. (That's what I am currently
doing.)
cStringIO is strictl
first ,thanks Dino a lot.
bellowing is not implement functions:
close
closed
flush
isatty
next
readlines
reset
softspace
tell
truncate
writelines
___
雅虎1G免费邮箱百分百防垃圾信
http://cn.mail.yahoo.com/
_
start_new, exit_thread and allocate all appear to be undocumented and their
__doc__ says they're just obsolete synonyms, which explains how we missed them.
But yes, we can make these call the correctly named versions so that old
scripts don't have to be modified. I've opened a beta 7 bug for th
Yes, it should be possible - .NET provides us the Stopwatch class for this
reason in 2.0. I've opened a beta 7 bug for this.
Do you want to help develop Dynamic languages on CLR?
(http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038)
-Original
Ahh, we'll want to consider routing that output through sys as well - it's a
little more complicated for the super console though.
Do you want to help develop Dynamic languages on CLR?
(http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038)
-Ori
The builtin IronPython thread module (./IronPython/Modules/thread.cs)
is missing several module functions, such as 'start_new',
'exit_thread' and 'allocate'. (see below)
The missing 'start_new' is causing some cpython scripts not to run for
me on IronPython. Is this going to be fixed for 1.0?
CP
Hello all,
I was surprised to note that the IronPython module provides dramatically
less resolution than the cPython equivalent.
Both ``time.time()`` and ``time.clock()`` provide a resolution of only
tenths of a second.
This module is obviously heavily dependent on the underlying platform.
In
