Bug 681417 - Warning: WebOb 1.0.3 Potentially Issues with TurboGears 2.1 + formencode
Summary: Warning: WebOb 1.0.3 Potentially Issues with TurboGears 2.1 + formencode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-webob
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ricky Zhou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 03:46 UTC by BJ Dierkes
Modified: 2011-08-18 10:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-18 10:22:28 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description BJ Dierkes 2011-03-02 03:46:49 UTC 
Description of problem:

When working in a dev environment (virtualenv --no-site-packages) I had a major failure in my TurboGears 2.1 application.  I've reported this issue upstream:

https://bitbucket.org/ianb/webob/issue/4/webob-103-breaks


This bug report (here at bugzille.redhat.com) is simply a warning, and a request to please watch the progress of that upstream bug to ensure there are no issues in rawhide.

I will be working to post an example TurboGears 2.1 project to demonstrate the issue upstream.... if I have a chance I will also try to test that against rawhide, or atleast python-webob-1.0.3 on F14.
Comment 1 Ricky Zhou 2011-06-01 07:23:22 UTC 
Sorry, I don't know how I missed this bug for so long.  CCing Luke Macken, who does more python-webob maintenance than I do nowadays.
Comment 2 BJ Dierkes 2011-06-01 18:47:50 UTC 
I forgot I created this bug also.  It should be noted that the issue was related to my use of a private object "environ['webob._parsed_post_vars']" which was resolved by using "webob.Request(env).str_POST" instead.  It should be safe to close this bugzilla after review.
Comment 3 Nils Philippsen 2011-08-18 10:22:28 UTC 
Closing as per comment #2.
Note You need to log in before you can comment on or make changes to this bug.