Leighton Chen

Re-opening to implement a more permanent fix. See [#903].

@jeremy010203 Good question. Changing the directory was not for fixing this issue. The SDK simply does not throw an error now if the folder already exists.

@mortendaehli Could you rebase and modify the `tox` file to not test on Py3.5?

Are you sending your requests via `requests.get(...)`? This could possibly be due to the `requests` extension wrapping the calls twice [here](https://github.com/census-instrumentation/opencensus-python/blob/master/contrib/opencensus-ext-requests/opencensus/ext/requests/trace.py#L90) and [here](https://github.com/census-instrumentation/opencensus-python/blob/master/contrib/opencensus-ext-requests/opencensus/ext/requests/trace.py#L161). The `requests.get` logic runs through both of...

@sudharc Can you simply remove the `trace_integration` for requests if you do not want these to be tracked?

@dsborets Hi, thanks so much for contributing! For (1), when you run `tox` locally, what error are you getting? For (2), try running `isort -rc .` on the root folder...

@fanshaohua-fan `AzureExporter` depends on the existence of `http.method`, `http.route` or `http.path` in the span attributes to populate the name field. It seems like `opencensus-ext-grpc` does not add these fields in...

@fanshaohua-fan That looks great! Feel free to submit a PR.

>When running via manage runserver I get data in Azure, only request data no database query tracing. To trace requests to the `postgresql` database, you must instrument with the [postgresql](https://github.com/census-instrumentation/opencensus-python/tree/master/contrib/opencensus-ext-postgresql)...

> I get data in Azure, only request data no database query tracing. So you are NOT getting database query tracing with just `manage runserver`? > If I set the...