Dario Castañé

#2410 was merged yesterday into main. It'll be released in the next weeks as part of v1.61.0.

@marcind We are implementing it in #2498. It'll be released in our next major v2 version during the current quarter.

We understand this is not longer required, and therefore this can be closed.

@jared-mackey Thanks for reaching out! We are going to review it.

Any ETA for releasing a Django 1.11 compatible version? Thanks!

As several others, I created a fork. My forks has support for Django 1.11 and 2.x from other forks and a minor fix to avoid django's Javascript global var conflicts:...

I upgraded it to Django 2.x and I use Python 3.7. That's why you got this error. Maybe we can work out a compatible version with both versions. I'm sorry...

@andreyshipilov, fixed and released as v0.3.5.

@jvorcak, it looks I forgot to update the README in order to point to my own PyPI package: [django-geoposition-2](https://pypi.org/project/django-geoposition-2/).

Notes about benchmarks: **scenario:BenchmarkOTelApiWithCustomTags/datadog_otel_api-24** As reported in March 14: - 🟥 allocations [+3; +3] or [+10.000%; +10.000%] - 🟥 execution_time [+453.667ns; +514.533ns] or [+8.967%; +10.170%] The extra allocations are: -...