-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
URL routing test that fails currently. #186
Conversation
…ad of streams for make_line/chunk_iter
According to RFC3987, percent-encoded parts are valid in IRIs as well as in URIs and do not need to be additionaly encoded.
Add convenience method to access the full path.
…epred in debugger: store a reference to the last repr'd object in '_' for easy reference; #166
Made a tiny grammar fix to tutorial
jace This patch will make the test go green. The general strategy is to update the heuristic the orders the rules so that the rules are ordered by:
there's a small weighting function that normalizes for the position of the part as well, but that is fairly minor. Please let me know what you think. |
It says "number of processes to spawn", but what it does is enable the SocketServer.ForkingMixIn which 'handles each request in a new process'. Its value is not the number of processes but the maximum number of processes that the ForkinMixIn will allow at the same time.
This seems to be a more typical usage.
If no author is given, don't generate an empty author tag anymore.
Add support for the "category" element to feed entries
contrib.atom: Fix empty author tag bug in FeedEntry.
Please use git-rebase to update your branch against master, to avoid that weird output in GitHub's web interface. |
contrib.atom: Fix copy and paste error in docstring
Change the example in parse_options_header
Remove a duplicate line
Comment fix
… into 0.8-maintenance
I'm now using my branch of werkzeug (with @jasonLaster's patch) for my production deployments Hoping this makes into @mitsuhiko's release. |
Found a sorting error in @jasonLaster's patch. I'm getting this sequence in my URL map. This shouldn't happen:
Rule 3 should be above Rule 1. I'll close this pull request and attempt a clean fix on top of master. |
As described in issue #185.