deprecation warnings issued for the sets module

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install wimpiggy and xpra
2. issue xpra start :1111
3. examine the log file ~/.xpra/:1111.log

What is the expected output? What do you see instead?

no warnings are expected. as python3.1 approaches, it would be good to handle 
this.

What version of the product are you using? On what operating system?

using version 0.0.6 with python2.6

Please provide any additional information below.

these deprecation warnings are issued from two files wimpiggy/wm.py and 
wimpiggy/window.py. i've hacked together a patch file for the two files roughly 
based on how they manage this deprecation warning in mysqldb without resorting 
to a try block and catching a hard exception if frozenset doesn't exist.

Original issue reported on code.google.com by tokenmat...@gmail.com on 31 Jul 2010 at 4:17

Attachments:

• sets-module-deprecation-2.6.patch

[GoogleCodeExporter]

this is merely an enhancement, not a defect at this point

Original comment by tokenmat...@gmail.com on 31 Jul 2010 at 4:19

[GoogleCodeExporter]

Thanks, committed.

Original comment by njsmith@ucsd.edu on 31 Jul 2010 at 3:36

• Changed state: Fixed