[issue47174] Define behavior of descriptor-typed fields on dataclasses

Change by mike bayer : -- nosy: +zzzeek ___ Python tracker <https://bugs.python.org/issue47174> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44304] segmentation fault appeared in python 3.10.0b2

mike bayer added the comment: great news! Based on how many random factors were needed to reproduce as well as that it seemed to be gc related and appeared very suddenly, I had an intuition this was on the cpython side, thanks so much for doing this Pablo

[issue44304] segmentation fault appeared in python 3.10.0b2

mike bayer added the comment: yes, if I have time I will begin to undertake that, wanted to put it up here in case anyone has git bisect on speed dial for cpython. -- ___ Python tracker <https://bugs.python.org/issue44

[issue44304] segmentation fault appeared in python 3.10.0b2

mike bayer added the comment: if the issue is in greenlet this can be bounced back to https://github.com/python-greenlet/greenlet/issues/242 -- ___ Python tracker <https://bugs.python.org/issue44

[issue44304] segmentation fault appeared in python 3.10.0b2

New submission from mike bayer : segmentation fault related to object deallocation and traceback objects, is extremely difficult to reproduce and definitely appeared as of 3.10.0b2, does not occur in 3.10.0b1. linux and osx platforms are affected. The issue requires "greenlet==

[issue43484] valid datetimes can become invalid if the timezone is changed

mike bayer added the comment: > I don't really know why it would be a "security vulnerability", but presumably a library could either convert their datetimes to UTC as soon as they get them from the user if they want to use them as UTC in the future, or they could simply ref

[issue43484] we can create valid datetime objects that become invalid if the timezone is changed

New submission from mike bayer : So I'm pretty sure this is "not a bug" but it's a bit of a problem and I have a user suggesting the "security vulnerability" bell on this one, and to be honest I don't even know what any library would do to "prevent" this. Ba

[issue39457] Add an autocommit property to sqlite3.Connection with a PEP 249 compliant manual commit mode and migrate

mike bayer added the comment: I think this issue just discusses the naming of an attribute called ".autocommit". for the discussion for SQLite's unusual starting of transactions, that's all in two other issues: https://bugs.python.org/issue9924 https://bugs.python.org/issue1

[issue39457] Add an autocommit property to sqlite3.Connection with a PEP 249 compliant manual commit mode and migrate

mike bayer added the comment: > Under your proposal, the first line would be changed to say > "autocommit=True", even though not all the code below is in autocommit mode > (according to the SQLite engine's definition). What's more, I could insert > this line of cod

[issue16535] json encoder unable to handle decimal

Change by mike bayer : -- nosy: +zzzeek ___ Python tracker <https://bugs.python.org/issue16535> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41629] __class__ not set defining 'X' as . Was __classcell__ propagated to type.__new__?

New submission from mike bayer : This is likely related or a dupe of https://bugs.python.org/issue29270, but the error message is different. I'm posting this to confirm it's the same issue, or not, and to at least provide a google result for people who also see this error as 29270 seems

[issue22239] asyncio: nested event loop

mike bayer added the comment: I tested "cancellation", shutting down the DB connection mid query. Because the greenlet is only in the middle and not at the endpoints, it propagates the exception and there does not seem to be anything different except for the greenlet sequence in

[issue22239] asyncio: nested event loop

mike bayer added the comment: as far as cancellation, I gather you're referring to what in gevent / greenlet is the GreenletExit exception. Sure, that thing is a PITA. Hence we're all working to provide asyncio frontends and networking backends so that the effects of cancellation I

[issue22239] asyncio: nested event loop

mike bayer added the comment: slight correction: it is of course possible to use gevent with a database driver without monkeypatching, as I wrote my own gevent benchmarks using psycogreen. I think what I'm getting at is that it's a good thing if async DBAPIs could target asyncio explicitly

[issue22239] asyncio: nested event loop

mike bayer added the comment: > Oh, I thought the primary problem for SQLAlchemy supporting async is that the > ORM needs to do IO from inside __getattr__ methods. So I assumed that the > reason you were so excited about greenlets was that it would let you use > await_() from

[issue22239] asyncio: nested event loop

mike bayer added the comment: > With greenlets OTOH, it becomes possible for another task to observe > someobj.a == 1 without someobj.b == 2, in case someobj.__setattr__ internally > invoked an await_(). let me try this one more time.Basically if someone wrote this: async def

[issue22239] asyncio: nested event loop

mike bayer added the comment: > With greenlets OTOH, it becomes possible for another task to observe > someobj.a == 1 without someobj.b == 2, in case someobj.__setattr__ internally > invoked an await_(). Any operation can potentially invoke a context switch. > So debugging gr

[issue22239] asyncio: nested event loop

mike bayer added the comment: yes so if you have async/await all internal, are you saying you can make that work for synchronous code *without* running the event loop? that is, some kind of container that just does the right thing? my concern with that would still be performance.When

[issue22239] asyncio: nested event loop

mike bayer added the comment: > This recipe was one of the reasons why I added `loop.set_task_factory` > method to the spec, so that it's possible to implement this in an *existing* > event loop like uvloop. But ultimately asyncio is flexible enough to let > users use their ow

[issue22239] asyncio: nested event loop

mike bayer added the comment: hey there, I seem to have two cents to offer so here it is.An obscure issue in the Python bug tracker is probably not the right place for this so consider this as an early draft of something that maybe I'll talk about more elsewhere. > This basica

[issue38749] sqlite3 driver fails on four byte unicode strings coming from JSON_EXTRACT

mike bayer added the comment: silly me thinking python devs had better access to SQLite devs :) -- ___ Python tracker <https://bugs.python.org/issue38

[issue38749] sqlite3 driver fails on four byte unicode strings coming from JSON_EXTRACT

mike bayer added the comment: Hi where did you report it?I don't see it on the mailing list or in their fossil tracker. -- ___ Python tracker <https://bugs.python.org/issue38

[issue38749] sqlite3 driver fails on four byte unicode strings coming from JSON_EXTRACT

New submission from mike bayer : When using unicode characters inside of JSON strings, values retrieved via the JSON_EXTRACT SQLite function fail to be decoded by the sqlite3 driver if they include four-byte unicode characters. Version information for my build, which is Fedora 30: Python

[issue37010] Review performance of inspect.getfullargspec

mike bayer added the comment: thanks for creating this issue Nick! -- nosy: +zzzeek ___ Python tracker <https://bugs.python.org/issue37010> ___ ___ Python-bug

[issue36751] Changes in the inspect module for PEP 570

mike bayer added the comment: Just did some benchmarks, and while Signature has apparently had a big speedup in Python 3.6, it is still much less performant than either the Python 2.7 or Python 3.3 implementations, anywhere from 6-18 times slower approximately depending on the function

[issue36751] Changes in the inspect module for PEP 570

mike bayer added the comment: > We are talking again and again that we have a lot of old things in the > standard library but it seems that removing them is also a problem. I agree that the reason we have these deprecation warnings is so that we do get notified and we do fix them. I

[issue36751] Changes in the inspect module for PEP 570

mike bayer added the comment: > A deprecating warning doesn't hurt: you are still able to run your code. this is very much untrue in modern testing environments, as it is common that test suites fail on deprecation warnings, especially in libraries, to ensure downstream compatibility.

[issue36751] Changes in the inspect module for PEP 570

mike bayer added the comment: if a function continues to work correctly throughout the span of a Python X version, why does it need to be removed? I have a foggy memory but I don't seem to recall functions that were technically redundant being aggressively deprecated in the 2.x series

[issue36751] Changes in the inspect module for PEP 570

Change by mike bayer : -- nosy: +zzzeek ___ Python tracker <https://bugs.python.org/issue36751> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35398] SQLite incorrect row count for UPDATE

Change by mike bayer : -- nosy: +zzzeek ___ Python tracker <https://bugs.python.org/issue35398> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32998] regular expression regression in python 3.7

mike bayer <mike...@zzzcomputing.com> added the comment: for those watching this would be the findall() case which is consistent between pythons: import re for reg in [ 'VARCHAR(30) COLLATE "en_US"', 'VARCHAR(30)' ]: print(re.findall(r'(?: COLLATE.*)?$', reg

[issue32998] regular expression regression in python 3.7

mike bayer <mike...@zzzcomputing.com> added the comment: for now the quickest solution is to add "count=1" so that it only replaces once. -- ___ Python tracker <rep...@bugs.python.org> <https://b

[issue32998] regular expression regression in python 3.7

mike bayer <mike...@zzzcomputing.com> added the comment: also, removing the "?" is not an option for me. I need the brackets to be placed prior to the "COLLATE" subsection, but unconditionally even if the "COLLATE" section is not present. Looking at

[issue32998] regular expression regression in python 3.7

mike bayer <mike...@zzzcomputing.com> added the comment: can you point me to the documentation? -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue32998] regular expression regression in python 3.7

mike bayer <mike...@zzzcomputing.com> added the comment: correction, that's fedora 26, not 27 -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue32998] regular expression regression in python 3.7

New submission from mike bayer <mike...@zzzcomputing.com>: demo: import re inner = 'VARCHAR(30) COLLATE "en_US"' result = re.sub( r'((?: COLLATE.*)?)$', r'FOO\1', inner ) print(inner) print(result) in all Python versions prior to 3.7: VARCHAR(30

[issue14976] queue.Queue() is not reentrant, so signals and GC can cause deadlocks

mike bayer added the comment: > Here is a pure Python PoC patch that allows unbounded Queue and LifoQueue to > have reentrant put(). per http://bugs.python.org/msg275377 guido does not want an RLock here. -- ___ Python tracke

[issue14976] queue.Queue() is not reentrant, so signals and GC can cause deadlocks

mike bayer added the comment: yep, that's what im doing in my approach. though longer term thing, I noticed it's very hard to find documentation on exactly when gc might run. E.g. would it ever run if I did something innocuous, like "self.thread_id = None" (probably not). J

[issue14976] queue.Queue() is not reentrant, so signals and GC can cause deadlocks

mike bayer added the comment: SQLAlchemy suffered from this issue long ago as we use a Queue for connections, which can be collected via weakref callback and sent back to put(), which we observed can occur via gc.For many years (like since 2007 or so) we've packaged a complete copy

[issue26690] PyUnicode_Decode breaks when Python / sqlite3 is built with sqlite 3.12.0

mike bayer added the comment: i realized this is probably with my build overall. let me do some more testing and ill reopen if i can confirm this more closely. -- resolution: -> works for me status: open -> closed ___ Python tracke

[issue26690] PyUnicode_Decode breaks when Python / sqlite3 is built with sqlite 3.12.0

New submission from mike bayer: So I really don't know *where* the issue is in this one, because I don't know enough about the different bits. Step 1: Save this C program to demo.c: #include static PyObject * unicode_thing(PyObject *self, PyObject *value) { char *str; Py_ssize_t

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

mike bayer added the comment: @rian - your issue for this is http://bugs.python.org/issue9924. The implicit BEGIN in all cases will probably never be the default but we do need an option for this to be the case, in order to support SERIALIZABLE isolation

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

mike bayer added the comment: @Rian - implicit transactions are part of the DBAPI spec. Looking at the original description, the purpose of this bug is to not *end* the transaction when DDL is received. So there's no solution for "database is locked" here, other than pysqli

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

mike bayer added the comment: thanks for the merge! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23898 ___ ___ Python-bugs-list mailing list

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

mike bayer added the comment: my star went through. let's merge. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23898 ___ ___ Python-bugs-list

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

mike bayer added the comment: hi Yury - I did sign it earlier today. It should have been sent off to the person that manages that, at least that's what the email receipt said. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

mike bayer added the comment: It would be great if the patch could be attached to the issue as a patch file, including some tests. the mantra we all share. I'll take a look. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

mike bayer added the comment: patch w/ test -- keywords: +patch Added file: http://bugs.python.org/file38882/issue23898.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23898

[issue23898] inspect() changes in Python3.4 are not compatible with objects that implement special __bool__, __eq__

New submission from mike bayer: this bug appeared in Python 3.4.The inspect.classify_class_attrs compares the identity objects of unknown type using the `==` operator unnecessarily and also evaluates objects of unknown type assuming they return `True` for a straight boolean evaluation

[issue22956] Improved support for prepared SQL statements

mike bayer added the comment: prepared statements are, in proportion to the typical speed issues in Python (see my comparison benchmark at https://mail.python.org/pipermail/db-sig/2014-December/006147.html) a fairly small optimization that the DBAPI already allows for in an implicit sense

[issue22956] Improved support for prepared SQL statements

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22956 ___ ___ Python-bugs-list

[issue14847] AttributeError: NoneType has no attribute 'utf_8_decode'

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14847 ___ ___ Python-bugs-list

[issue22457] load_tests not invoked in root __init__.py when start=package root

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22457 ___ ___ Python-bugs-list

[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection

New submission from mike bayer: Per DBAPI and pysqlite docs, .description must be available for any SELECT statement regardless of whether or not rows are returned. However, this fails for SELECT statements that aren't simple SELECTs, such as those that use CTEs and therefore start out

[issue11380] Improve reporting of broken stdout pipe during interpreter shutdown

mike bayer added the comment: my users are reporting one of these issues, and while I can easily catch IOError on Python 2, I can't catch anything on Python 3, and pointing SIGPIPE to SIG_DFL isn't an option because this is for Alembic migrations and the command needs to complete its work

[issue20828] inspect.getargspec() returns wrong answer with datetime.today.__call__()

New submission from mike bayer: this appears like it may be related to http://bugs.python.org/issue20786, at least in terms of inspect.getargspec() seems to be returning answers in 3.4 where it used to raise TypeError, however like in 20786 it's again returning the wrong answer. I'm a little

[issue20786] inspect.getargspec() returns wrong answer with property.__delete__()

mike bayer added the comment: see also http://bugs.python.org/issue20828 as it seems like there might be a bigger pattern here (not sure). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20786

[issue20828] inspect.getargspec() returns wrong answer with datetime.today.__call__()

mike bayer added the comment: I've also worked around this on my end, so if my poking into today.__call__() isn't really a good idea anyway, I'm not doing that anymore. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20828

[issue20828] inspect.getargspec() returns wrong answer with datetime.today.__call__()

mike bayer added the comment: we basically need to be able to get the argument signature for anything that passes callable(); function, method, class, object with __call__. So this is the logic we use: import inspect def get_callable_argspec(fn): if inspect.isfunction(fn

[issue20828] inspect.getargspec() returns wrong answer with datetime.today.__call__()

mike bayer added the comment: I've got something like that going on right now, but am doing it in the other direction; when I look at __call__(), I only do anything with it if it passes inspect.ismethod(). Since I only want plain Python __call__() functions on plain Python objects

[issue20786] inspect.getargspec() returns wrong answer with property.__delete__()

New submission from mike bayer: The Python builtin property() historically does not allow inspect.getargspec to be called on any of __get__(), __set__(), or __delete__(). As of 3.4, it seems that this call now succeeds. However the answer it gives for __delete__() seems to be incorrect

[issue20786] inspect.getargspec() returns wrong answer with property.__delete__()

Changes by mike bayer mike...@zzzcomputing.com: -- components: +Library (Lib) type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20786

[issue20786] inspect.getargspec() returns wrong answer with property.__delete__()

mike bayer added the comment: for context, we are currently creating wrappers around these methods in SQLAlchemy, and in the case of property dunders, we expect that exception and catch it. So when the exception doesn't happen, we assume the answer is correct, but in this case it's

[issue17482] functools.update_wrapper mishandles __wrapped__

mike bayer added the comment: this is actually biting me, I think, though I'm having a very hard time getting a small Python script to duplicate it :/. https://bitbucket.org/zzzeek/alembic/issue/175/test-suite-failure-under-python34 refers to the current problems I'm having. I am

[issue17482] functools.update_wrapper mishandles __wrapped__

mike bayer added the comment: i think I found the problem. sorry for the noise. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17482

[issue17482] functools.update_wrapper mishandles __wrapped__

mike bayer added the comment: OK well, let me just note what the issue is, and I think this is pretty backwards-incompatible, and additionally I really can't find any reasonable way of working around it except for just deleting __wrapped__. It would be nice if there were some recipe

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

mike bayer added the comment: see also http://bugs.python.org/issue10740, which also relates to pysqlite attempting to make guesses as to when transactions should begin and end. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

mike bayer added the comment: well Adam, you might also be surprised to see pysqlite not doing very well on the *other* side of the equation either; that is, when it *begins* the transaction. Issue http://bugs.python.org/issue9924 refers to this and like this one, hasn't seen any activity

[issue10740] sqlite3 module should allow DDL statements in transactions

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10740 ___ ___ Python-bugs-list

[issue9253] argparse: optional subparsers

mike bayer added the comment: um, this seems like a regression/bug? I now have users complaining that my apps are broken because of this change as of Python 3.3.My application is supposed to return the help screen when no command is given. Now I get a None error because argparse

[issue16389] re._compiled_typed's lru_cache causes significant degradation of the mako_v2 bench

mike bayer added the comment: in response to ezio, I poked around the source here, since I've never been sure if re.compile() cached its result or not. It seems to be the case in 2.7 and 3.2 also - 2.7 uses a local caching scheme and 3.2 uses functools.lru_cache, yet we don't see as much

[issue1062277] Pickle breakage with reduction of recursive structures

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1062277 ___ ___ Python-bugs-list

[issue7511] msvc9compiler.py: ValueError: [u'path']

mike bayer mike...@zzzcomputing.com added the comment: I think it's fair to ask the user to setup the environment correctly before running python setup.py install We're supporting automatic fallback to non-C install for those environments that don't support it. We're just looking

[issue7511] msvc9compiler.py: ValueError: [u'path']

mike bayer mike...@zzzcomputing.com added the comment: regarding hey this is an MS bug not Python, projects which feature optional C extensions are starting to apply workarounds for the issue on their end (I will need to commit a specific catch for this to SQLAlchemy) - users need to install

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

New submission from mike bayer mike...@zzzcomputing.com: Copying this bug from the pysqlite tracker, at http://code.google.com/p/pysqlite/issues/detail?id=21 , as the issue has been opened for two days with no reply. (side node - should sqlite3 bugs be reported here or on the pysqlite tracker

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

mike bayer mike...@zzzcomputing.com added the comment: My own comment here is that I'm supposing the late BEGIN behavior is to cut down on SQLite's file locking.I think a way to maintain that convenience for most cases, while allowing the stricter behavior that makes SERIALIZABLE

[issue9405] crash when calling urllib.getproxies() under OSX with subprocess / particular memory usage

mike bayer mike...@zzzcomputing.com added the comment: Yeah we are fine if I build the release2.7-maint branch.Also just noticed that this bug prevents really basic things, like using urllib2 from a Pylons application that's running in daemon mode. Pretty major, though unusual that I

[issue9405] crash when calling urllib.getproxies() under OSX with subprocess / particular memory usage

New submission from mike bayer mike...@zzzcomputing.com: I'm not optimistic that this will be reproducible elsewhere. I get a silent failure with 2.6 and a crash dialog with 2.7 with the following script. All elements are necessary, although the pkg_resources import may be arbitrary

[issue9405] crash when calling urllib.getproxies() under OSX with subprocess / particular memory usage

mike bayer mike...@zzzcomputing.com added the comment: right...so I would propose the function calls in question emit a warning or something when called in a child process. this would save lots of people many hours of grief. -- ___ Python tracker

[issue9269] Cannot pickle self-referencing sets

mike bayer mike...@zzzcomputing.com added the comment: where is it defined that sets are not supposed to contain mutable items? such a requirement vastly limits the usefulness of sets. Consider that relational database rows are mutable. A result set containing multiple rows which each have

[issue9269] Cannot pickle self-referencing sets

mike bayer mike...@zzzcomputing.com added the comment: OK, more specifically, here's the kind of situation where items in a set are mutable: company = Session.query(Company).first() # company.employees is a set() company.employees # each employee references the parent company for e

[issue7922] Python 3's 2to3 does not handle non-ascii source files

New submission from mike bayer mike...@zzzcomputing.com: given the following Python 2 source file: # -*- encoding: utf-8 print 'bien mangé' It can be converted to Python 3 using 2's 2to3 tool: classic$ 2to3 test.py ... omitted ... --- test.py (original) +++ test.py

[issue7922] Python 3's 2to3 does not handle non-ascii source files

mike bayer mike...@zzzcomputing.com added the comment: yes, its handled: WARNING: couldn't encode test.py's diff for your terminal is that fix specific to 2to3 or is that just how print works in 3.2 ? -- ___ Python tracker rep...@bugs.python.org

[issue6245] Add intel universal architecture on OSX

Changes by mike bayer mike...@zzzcomputing.com: -- nosy: +zzzeek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6245 ___ ___ Python-bugs-list

[issue998998] pickle bug - recursively memoizing class?

mike bayer mike...@zzzcomputing.com added the comment: im noticing my test case seems to work fine in py 3.0.1. haven't tested 2.6.2. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue998998

[issue6149] WeakValueDictionary constructor ported to Python 3.0 incorrectly

New submission from mike bayer mike...@zzzcomputing.com: The constructor for WeakValueDictionary does not obey the contract documented in its comments: # We inherit the constructor without worrying about the input # dictionary; since it uses our .update() method, we get the right

[issue6149] WeakValueDictionary constructor ported to Python 3.0 incorrectly

Changes by mike bayer mike...@zzzcomputing.com: -- components: +Library (Lib) type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6149

[issue5331] multiprocessing hangs when Pool used within Process

New submission from mike bayer mike...@zzzcomputing.com: this occurs for me running on Mac OSX Leopard. The equivalent code using processing in python 2.5 works fine, which is how I found this bug - my code hung when upgraded to 2.6.Basically initiating a multiprocessing.Pool inside

[issue998998] pickle bug - recursively memoizing class?

mike bayer [EMAIL PROTECTED] added the comment: This bug can be reproduced very easily: import pickle class MyClass(object): pass m = MyClass() m2 = MyClass() s = set([m]) m.foo = set([m2]) m2.foo = s print pickle.dumps(s) This bug is critical