This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zzzeek
Recipients alexandre.vassalotti, belopolsky, eric.araujo, grubert, jackdied, rhettinger, schmir, zzzeek
Date 2010-07-16.02:05:29
SpamBayes Score 0.0048079104
Marked as misclassified No
Message-id <>
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()

# each employee references the parent company
for e in company.employees:
    assert is company

So nothing is mutated relationally in this case.   It's just a plain old bidirectional structure.    If two objects are related via many-to-many, then you might have a set in both directions.   I'm not sure if this specific situation produces the pickle bug, however, it's been awhile since I've seen which specific case causes the problem.   But there are mutable items in a set in these examples and it doesn't seem unreasonable to me.
Date User Action Args
2010-07-16 02:05:33zzzeeksetrecipients: + zzzeek, rhettinger, belopolsky, grubert, jackdied, alexandre.vassalotti, schmir, eric.araujo
2010-07-16 02:05:33zzzeeksetmessageid: <>
2010-07-16 02:05:31zzzeeklinkissue9269 messages
2010-07-16 02:05:29zzzeekcreate