DispatcherMiddleware fabricates environments for your apps and especially SCRIPT_NAME. Django can deal with it with configuration varibale FORCE_SCRIPT_NAME = '' (docs).

With Webapp2 it's slightly more complicated. You can create subclass of webapp2.WSGIApplication and override __call__() method and force SCRIPT_NAME to desired value. So in your webapp2_app.py it could be like this

import webapp2

class WSGIApp(webapp2.WSGIApplication):

    def __call__(self, environ, start_response):
        environ['SCRIPT_NAME'] = ''
        return super(WSGIApp, self).__call__(environ, start_response)

# app = WSGIApp(...)

SOLUTION:

I was using wrong tha same name for the dispacher and the app1.

dispacher.py should be edited as follows:

from flask import Flask
from werkzeug.wsgi import DispatcherMiddleware
from werkzeug.exceptions import NotFound

from app1 import app as app1


app = Flask(__name__)

app.wsgi_app = DispatcherMiddleware(NotFound(), {
    "/prefix": app1
})

if __name__ == "__main__":
    app.run()

Aptitude is often woefully out of date for Python packages, as it seems to be here. You are much better off using pip, Python's package management tool. Pip tells me that werkzeug is currently at version 0.8.1!

First install pip (if you don't have it already)

sudo easy_install pip

Then install werkzeug

sudo pip install werkzeug

Easy install is no longer the recommended way to do Python package - you should certainly be using pip.

These commands install the packages into your machine's global Python environment. You would do well to investigate virtualenv, which creates separate Python interpreters that can have their own packages installed.

Good luck!

I've come to the conclusion that this is a stupid idea that is very fragile and requires a lot of unnecessary complexity. I've instead just opted to write a bash script that starts all the apps as separate wsgi instances on their own port.