Martin Maly wrote:
Hi Michael,
...
I can see your emails just came through... Since you have spent the time
and modified the tests so that they can readily run on IronPython,
filing the actual bugs is not necessary because we can simply run your
modified test and fix whatever the test indicates fai
Martin Maly wrote:
Hi Michael,
...
I can see your emails just came through... Since you have spent the time
and modified the tests so that they can readily run on IronPython,
filing the actual bugs is not necessary because we can simply run your
modified test and fix whatever the test indicates fai
> from: Jim Hugunin
>
> I know that I've been very quiet with answering questions
> about the license used for IronPython. This is primarily
> because I'm not the right person to be addressing these
> questions. Jason Matusow, MS's director of shared source,
> has been blogging about this li
> Keith J. Farmer Wrote:
> Well, since these tests will be viewed by many to be the standard, do
> the tests planned include a superset of these, at least?
Yes.
> I was making a haphazard estimate of the timing for 1.0, figuring a
> two-week cycle, going no further than 0.0.x, would give up to 60
Hi Michael,
I did not perceive your original email as critical or emphasizing
failures and I am really glad that you took the effort to run the tests.
I also realize that the original request for bug reports was not very
clear and that is why I used this opportunity to clarify that we are
working
A few years ago, I
created an AppBar by merging wxPython, what became PyCrust, and the win32
extensions. I just realized how much easier it'll be to re-create that
(and how much more likely it'll be to work correctly). The old project is
here:
http://www.thuban.org:8080/projects/PyA
I know that I've been very quiet with answering questions about the
license used for IronPython. This is primarily because I'm not the
right person to be addressing these questions. Jason Matusow, MS's
director of shared source, has been blogging about this license over the
past week and now has
Test Module (a couple of hacks to CPython test_builtin to enable it to import
and run on fepy 0.7.1)
# Python test set -- built-in functions << this is line 1 of the source
#import test.test_support, unittest
#from test.test_support import fcmp, have_unicode, TESTFN, unlink
have_unicode = False
i
Results Detail
>>> T.formatfepyfailures(res)
14 Tests failed:
IronPython.Objects.PythonAssertionError: ValueError
at IronPython.Objects.Ops.Raise(Object type, Object value, Object traceback)
at unittest.failUnlessRaises$f172(Object self, Object excClass, Object callab
leObj, Object args, Obj
+1 for ironpy
On Fri, 1 Apr 2005 00:46:35 +0200, R.R. Sprinkhuizen
<[EMAIL PROTECTED]> wrote:
>
>
> > Personally, I like ironpy. I too was a little late in voting ;-)
>
> Count me in. I don't like fepy.
>
> > I'm happy we're getting new releases at all, frankly.
>
> Me too, but very unhapp
Martin Maly wrote:
Hi Michael,
Thank you for taking the time and running the test suite. It is not
surprising that there are so many failures since much of the development
effort went into getting basic functionality and interoperability with
.Net framework and there are many cases (some are common
There is known issue with indexing where IronPython may have trouble finding
the right indexer.
This may be what you are hitting. I am not familiar with Npgsql, but on .Net
classes there is
often property that you can access directly and bypass the access by index.
Martin
> On Monday, April 04,
Well, since these tests will be viewed by many to be the standard, do
the tests planned include a superset of these, at least?
I was making a haphazard estimate of the timing for 1.0, figuring a
two-week cycle, going no further than 0.0.x, would give up to 60 weeks
for 1.0 release. I'm guessing y
Hi Michael,
Thank you for taking the time and running the test suite. It is not
surprising that there are so many failures since much of the development
effort went into getting basic functionality and interoperability with
.Net framework and there are many cases (some are common, some less)
that
There were issues with float point parsing
in IronPython 0.6. You can use the newest available release 0.7.1 which has
these issues fixed (I just ran your commands on the newest release)
The newest IronPython 0.7.1 can be
downloaded from:
http://workspaces.gotdotnet.com/ironpython
IronPython 0.6
>>> type (1e-1)
>>> type (0.1)
>>> 1e-1
0,1
>>> 0.1
1
>>> 1e-1*2
0,2
>>> 0.1*2
2
>>>
___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Hello friends, I am using Npgsql, from IronPython functions, but I do not be able optener data of the results, some idea of as I can do it?
Conn = Npgsql.NpgsqlConnection("Server=127.0.0.1;Port=5432;User Id=miuler;Password=miuler;Database=basecsd;")
Conn.Open()
Cmd = Npgsql.NpgsqlCommand
On Apr 4, 2005 3:50 AM, Nicolas Lehuen <[EMAIL PROTECTED]> wrote:
> BTW, this module list is far from exhaustive... There are many others,
> not speaking about the dependencies on core python modules (for
> example, the medusa async I/O HTTP Server) which are not implemented
> yet. And Plone adds
BTW, this module list is far from exhaustive... There are many others,
not speaking about the dependencies on core python modules (for
example, the medusa async I/O HTTP Server) which are not implemented
yet. And Plone adds another layer of dependencies on native code and
Python modules.
I guess
Hi,
As far as I know, there is a bunch of Python module written in C at
the core of Zope. They implement the core capacities of the object
broker and the object database engine :
Acquisition.pyd
Btree.pyd
ComputedAttribute.pyd
ExtensionClass.pyd
IIBtree.pyd
initgroup.pyd
intSet.pyd
IOBTree.pyd
Me
What are the prospects for running Zope on
IronPython?
Having Zope run on .NET could open up some quite
interesting possibilities, esp. for Plone, the popular content management system
(CMS) for Zope. I usually work with .NET, but for some CMS stuff I did I chose
Plone. I liked that a lot
Already taken
--
Keith J. Farmer
[EMAIL PROTECTED]
http://www.thuban.org
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anthony Tarlano
Sent: Monday, April 04, 2005 3:12 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Renaming IronPyt
Another thought is just name it python.net and be done with this iron stuff..
Anthony
On Apr 3, 2005 10:26 AM, R.R. Sprinkhuizen <[EMAIL PROTECTED]> wrote:
> For the record, I changed my "whining" strategy just yesterday by getting
> and installing 2.0-beta. I guess if I like IronPython (which is
Has someone made binaries of the lastest mono for win32, with 2.0
preview on, to run IronPython with?
--
Keith J. Farmer
[EMAIL PROTECTED]
http://www.thuban.org
___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http:
First cut result at a hacked version of cpython's test_builtin. Some changes
required to this and unittest to import successfully.
Below you will find results summary. Results detail, then the test module
itself will follow in subsequent posts
G:\CABS\Python\FePy\IronPython-0.7.1\bin>IronPytho
25 matches
Mail list logo
