Skip to content
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

Closed
wants to merge 86 commits into from
Closed

URL routing test that fails currently. #186

wants to merge 86 commits into from

Conversation

jace
Copy link
Contributor

@jace jace commented May 8, 2012

As described in issue #185.

mitsuhiko and others added 30 commits September 29, 2011 23:35
According to RFC3987, percent-encoded parts are valid in IRIs as well as in URIs and do not need to be additionaly encoded.
@jasonLaster
Copy link

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:

  1. number of static parts
  2. number of variable parts
  3. number of paths

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.

Conor Hennessy and others added 8 commits July 3, 2012 05:13
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.
@untitaker
Copy link
Contributor

Please use git-rebase to update your branch against master, to avoid that weird output in GitHub's web interface.

@jace
Copy link
Contributor Author

jace commented Dec 13, 2012

I'm now using my branch of werkzeug (with @jasonLaster's patch) for my production deployments Hoping this makes into @mitsuhiko's release.

@jace
Copy link
Contributor Author

jace commented Jan 2, 2013

Found a sorting error in @jasonLaster's patch. I'm getting this sequence in my URL map. This shouldn't happen:

 <Rule '/<workspace>/reports/<report>' (HEAD, POST, OPTIONS, GET) -> report>,
 <Rule '/<workspace>/reports/' (HEAD, OPTIONS, GET) -> reports>,
 <Rule '/<workspace>/reports/new' (HEAD, POST, OPTIONS, GET) -> report_new>,

Rule 3 should be above Rule 1. I'll close this pull request and attempt a clean fix on top of master.

@jace jace closed this Jan 2, 2013
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.