id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
124	"""sets"" module is deprecated in py2.6"	Brian Warner		"Running foolscap under python2.6 provokes a deprecation warning, because the old ""sets"" module (added in py2.3 and obsoleted with the builtin set/frozenset types in py2.4) has finally been deprecated.

To hush the warning in py2.6, we need to stop importing ""sets"". However, doing that will cause us to stop being compatible with code that was written to be compatible with py2.3 (by using e.g. sets.ImmutableSet instead of frozenset), even if that code is now only run against py2.4 or py2.5 .

If this py2.3-py2.5 code imports the ""sets"" module, then we'll need to be able to serialize any Set or ImmutableSet instances that it creates, so we need to be able to recognize those classes as slicing time. (on the deserialization side, we turn these into set and frozenset, so it doesn't matter at unslicing time).

I suppose the answer is to give up on compatibility with this sort of code, but it makes me feel bad: Foolscap's desire to be less noisy with py2.6 might push someone who wasn't trying to use py2.6 to give up on their py2.3 users.

I'm going to put off fixing this for a little while, maybe a release or two.
"	defect	closed	minor	0.5.0	unknown	0.3.0	fixed