Hi all
I'm very happy to announce the latest release (candidate) of Ironclad,
the 120-proof home-brewed CPython compatibility layer, now available
for IronPython 2.6!
No longer need .NET pythonistas toil thanklessly without the benefits
of bz2, csv, numpy and scipy: with a simple 'import ironclad
Hi all
I'm fairly pleased to announce the release of Ironclad v0.8.1; it's not
an enormous technical leap above v0.8, but it does now enable you to
import and use SciPy and Matplotlib with IronPython on Win32 (with some
restrictions; see project page) . Downloads, and more details, are
availab
Hi all
We're about to release the first public beta of Resolver One, our
Pythonic spreadsheet, with (rather basic) NumPy integration. It requires
32-bit Windows and .NET 2.0SP1 to run, so it may not be appropriate for
everyone, but -- if anyone is interested in playing with it -- it would
be r
Hi Tim
Thank you for your interest! To answer your various questions order
of approximately increasing complexity:
Most importantly: the currently available version of Resolver One
does not have numpy support built in, and for various reasons I
wouldn't advise trying to integrate Ironclad w
Hi all
I'm delighted to announce the release of Ironclad v0.8 -- the
all-singing, all-dancing CPython API compatibility layer for IronPython
-- available now from http://code.google.com/p/ironclad/ . Notable
improvements over the last release include:
* Ironclad is now a neatly self-contained
Hi all
Hopefully someone here will be interested in this, and it won't be
considered too spammy... please let me know if this isn't welcome, and
I'll desist in future.
I'm delighted to announce the release of Ironclad v0.7, which is now
available from http://code.google.com/p/ironclad/download
That's great news -- thank you very much
William
Stéfan van der Walt wrote:
> 2008/8/21 William Reade <[EMAIL PROTECTED]>:
>
>> Line 532 of numerictypes.py reads "_unicodesize =
>> array('u','U1').itemsize", but _unicodesize i
Travis E. Oliphant wrote:
> I don't know the answer to these questions.
>
Thanks for your response -- can anyone suggest a better forum for these
sorts of issues?
> I would say that unicode arrays are rare and I would definitely work on
> floating-point first.Any chance we can see some o
Hi
I hope this is the right place for this question... if not, I apologise,
and ask only that you please direct me somewhere more appropriate.
Line 532 of numerictypes.py reads "_unicodesize =
array('u','U1').itemsize", but _unicodesize itself does not appear to be
referenced anywhere else. My
