[IronPython] Semi-blocking bug in IP 2B1

Dino Viehland dinov at exchange.microsoft.com
Mon Mar 31 18:17:06 CEST 2008

I've created a bug for this - http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=15882

Given that it's a pretty bad regression I'll take a look at it after I finish up the work I'm doing on startup perf right now.

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Michael Foord
Sent: Monday, March 31, 2008 8:10 AM
To: Resolver Developers; Discussion of IronPython
Subject: [IronPython] Semi-blocking bug in IP 2B1

Hello all,

There is a bug in dictionaries in IronPython 2 beta 1. I found this
trying to port Resolver One to IP 2. Whilst I can work round it in this
case I wonder how many times this bug will bite us in our code base:

 >>> d = dict()
 >>> d[0, 0] = 3
 >>> del d[0, 0]
Traceback (most recent call last):
  File , line unknown, in Initialize##345
TypeError: __delitem__() takes exactly 1 argument (2 given)

In general, error reporting/tracebacks seem to be much worse in
IronPython 2. If I have time I will try and produce a repro...


Michael Foord
Senior Software Engineer, Resolver Systems Ltd.
michael.foord at resolversystems.com
+44 (0) 20 7253 6372

We're hiring! http://www.resolversystems.com/jobs/
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329.
Registered address: 843 Finchley Road, London NW11 8NA, UK

Users mailing list
Users at lists.ironpython.com

More information about the Ironpython-users mailing list