Marcel Hellkamp

We can phase out support for old Python versions as soon as these reach EOL, but not before that. For master this means: We can stop testing against dead python...

Are you sure that this does the same thing? Note that the search list is mutated within the loop.

The two strings `%2F` and `/` are equivalent in an URI path. You can encode any character this way. `a` equals `%61` for example.

Oh, the `:path` filter works just fine. I cannot reproduce the error. ``` >>> import bottle >>> app = bottle.Bottle() >>> app.route('/resources//container//items', callback=True) >>> app.match(dict(PATH_INFO='/resources/adfs89s7/container/asdf%2Fasdf/items', REQUEST_METHOD='GET')) (..., {'resource_id': 'adfs89s7', 'container_name':...

I still cannot reproduce this bug in master or release-v12: ``` >>> import bottle >>> app = bottle.Bottle() >>> app.route('/test/', callback=True) True >>> app.match(dict(PATH_INFO='/test/123/asd', REQUEST_METHOD='GET')) (, {'test': '123/asd'}) >>> app.match(dict(PATH_INFO='/test/123%2Fasd',...

I often thought about that but the single-source-file strategy has benefits, too: It avoids bloated and unreadable code and makes me thing twice before adding more features or applying unmatured...

I think some kind of build-process and a split-out of pats of the bottle framework is inevitable by now. The multipart-parser for example (#80) is quite useful on its own...

I started reordering and refactoring the bottle sources to prepare the split. The process involves some touch design decisions, so don't hold your breath :)

Sorry, but we try to do accept new adapters only if there is a significant demand for it. There are just to many WSGI servers and forks out there to...

I'll reopen for a public discussion.