New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BaseCookie should call value_decode from __getitem__ #41770
Comments
Perhaps I'm misunderstanding its functionality, but I |
Well should it or shouldn't it? |
No reply to msg109888. |
Mark, not many people follow the full bugs list (I'm don't anymore...I just happened to notice this one going by on the IRC channel). Asking a question without adding appropriate people to nosy is therefore not all that likely to obtain a response, and a lack of response in that situation is not, IMO, sufficient grounds for closing an issue. If you can't find someone to add to nosy, you could post to python-dev. From a look at the code it appears to me that this is not valid. value_decode is called by __ParseString which is called from 'load'. The cookies are apparently stored in the dict as a Morsel that contains a both a 'real value' and the 'encoded value', and those pairs get created via individual sets (the call to __setitem__), when a load-from-string is done, or by *encoding* the real values when a load-from-dict is done (ie: a mass __setitem__). It seems like closing this as invalid is the correct action; however, the OP clearly observed a problem, but we don't have sufficient information to diagnose it. Ryan, if you are still interested in/seeing this problem, can you supply a test case that demonstrates the issue you observed? Otherwise we'll close the issue. |
Nor reply to msg114679. |
Moreover, BaseCookie should be used only for subclassing. Proper way is to always use SimpleCookie, this was an Invalid bug report. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: