[IronPython] Bug in copy module (really need help with this!) :)
michael at voidspace.org.uk
Tue Oct 12 16:43:45 CEST 2010
On 12/10/2010 15:29, Pablo Dalmazzo wrote:
> Hello guys,
> we've found a bug in the copy module, but the real problem is we cant
> reproduce it.
> Sometimes when we try to deepcopy an object of a custom object
> relation mapping type, we get this error
> "name types is not defined"
> Line 55:
> for t in (type(None),int,long,float,bool,str,tuple),
In my version of Python 2.6 this is line 102 of the copy module. Line 51
is "import types", so a "name types is not defined" error is most
perplexing. Is it possible that you are using a custom version of the
All the best,
> the other problem is in production server, where this error uses to
> happen sporadically, most times we dont get this message but an error
> message of the most outer module which calls the copy module, which is
> a generic message which tells us nothing
> I know this is very little information to find a bug but, do you know
> of any bugs related to the module copy (aside it didnt copy
> System.DBnull which I believe it's not the one for this case)
> Greetings, Pablo Dalmazzo
> Users mailing list
> Users at lists.ironpython.com
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies ("BOGUS AGREEMENTS") that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users