| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Release as a universal wheel
|
|/
|
|
| |
By releasing as a [Python wheel](http://pythonwheels.com/) as well as a source distribution, you can speed up end user’s installs. After merging this command, to release you just need to run `python setup.py clean sdist bdist_wheel upload`.
|
|\
| |
| | |
Fix tox comment next to nose dependency
|
| |
| |
| |
| |
| | |
It looks tox stopped understanding comments, added to the same line
as instructions. Work around that.
|
| |\
| | |
| | | |
Update from upstream #3
|
|\ \ \
| |_|/
|/| | |
Fix a little syntax error
|
|/ / |
|
|\ \
| | |
| | | |
Convert readthedocs links for their .org -> .io migration for hosted projects
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per [their blog post of the 27th April](https://blog.readthedocs.com/securing-subdomains/) ‘Securing subdomains’:
> Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard.
Test Plan: Manually visited all the links I’ve modified.
|
|\ \ \
| |/ /
|/| | |
Fix missing quotes in documentation
|
|/ /
| |
| |
| |
| | |
When reading the docs I discovered a missing set of single quotes in
this code example which makes the example invalid python code. Fixed.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Tolerate older usage with mandatory routename and optional path
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the following review:
https://github.com/bbangert/routes/commit/0a417004be7e2d950bdcd629ccf24cf9f56ef817
Routes 2.3 has changed the function signature to mandate
path in addition to routename for the connect method.
In this patch, we try to get back to path being optional by
checking the length of the args list. No other change in
logic.
This hopefully fixes the problem reported here:
https://github.com/bbangert/routes/issues/64
Add an entry in Changelog as well.
|
| | |
|
|\ \
| | |
| | | |
Fix typo
|
|/ / |
|
|\ \
| | |
| | | |
Fix subdomain equivalence check
|
| | | |
|
|/ /
| |
| |
| |
| | |
Problem occurred when new subdomain was left substring of current one.
In this case subdomain was not replaced.
|
|\ \
| | |
| | | |
Fix #29. Add support for protocol-relative URLs
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |/
|/| |
Update from upstream #2
|
|\ \
| | |
| | | |
Fix #38: Add webob dependency [optional]
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |/
|/| |
Update from upstream
|
|\ \
| | |
| | | |
Add tox.ini
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tox is a nice tool to run tests: it creates virtual environments,
install test dependencies and run tests. With the simple command
"tox", tests are run on Python 2 and Python 3.
* Create tox.ini based on .travis.yml
* Modidy .travis.yml to use tox-travis:
https://github.com/ryanhiebert/tox-travis
* .gitignore: ignore .tox/ sub-directory created by tox.
|
|\ \
| | |
| | | |
Fix BytesWarning in Mapper.generate()
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When python3 is run with -bb, str(bytes) raises a BytesWarning. On
Python 3, Mapper.generate() gets such BytesWarning because
script_name type is str whereas cache_key type is byte.
On Python 3, generate() now encodes the script_name to UTF-8 and uses
bytes concatenation to fix this issue.
.travis.yml: Run tests using "python -bb $(which nosetests)" to raise
BytesWarning exception on bytes vs Unicode issue.
|
|\ \
| |/
|/| |
Fix empty string match
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
allow requirements to be specified on Mapper.resource
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for ``requirements`` option to mapper.resource,
which makes it possible to restrict matching in urls (most often
useful for capturing variables with path_prefix).
In OpenStack Nova we've used the prefix_path on Mapper.resource to
specify additional variables we want to capture (specifically
{project_id}). Project_id is a uuid. When trying to restrict
project_id to only valid uuid format a couple of issues were exposed.
- #1 '/{project_id:[a-f0-9]{32}}/...' builds an incorrect regex
because of the nested {}
- #2 the preferred method that works on connect() to pass
requirements doesn't work here (requirements are reset to only an
id match)
That leaves us with having to build a custom project_id match with 32
[a-f0-9] strings appended for every resource added to get the support
we need without effectively vendoring our own version of Mapper.resource.
This small change to allow requirements to pass through would make it
possible to get this tighter validation with much smaller regexes.
|
| |
|
|\
| |
| | |
Concat fix
|
| | |
|