[ moin-Bugs-969500 ] UnpicklingError undeclared in 1.2.2

"SourceForge.net" <[email protected]>
Newsgroups gmane.comp.web.wiki.moin.devel
Message-ID <[email protected]>
Bugs item #969500, was opened at 2004-06-09 10:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108482&aid=969500&group_id=8482

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jure Koren (stibbons)
Assigned to: Nobody/Anonymous (nobody)
Summary: UnpicklingError undeclared in 1.2.2

Initial Comment:
SuSE 9, Python 2.3+ (the default for suse 9), apache 2 with 
mod_python 3.1.3.

When creating a new user, I got the NameError about name 
'UnpicklingError' not being defined (the exception is defined in the 
pickle module, but not in the global module scope of user.py).

This is the patch that fixed the problem for me:

--- /home/jure/wiki/moin-1.2.2/build/lib/MoinMoin/user.py       
2004-06-06 01:58:39.000000000 +0200
+++ user.py     2004-06-09 12:02:21.709993524 +0200
@@ -46,7 +46,7 @@
         userdictpickle = os.path.join(config.user_dir, 
"userdict.pickle")
         try:
             _name2id = pickle.load(open(userdictpickle))
-        except (UnpicklingError,IOError,EOFError,ValueError):
+        except (pickle.UnpicklingError,IOError,EOFError,ValueError):
             _name2id = {}
     id = _name2id.get(searchName, None)
     if id is None:


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108482&aid=969500&group_id=8482


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.