thanks Chris and Milton.
I had a different error but it was so long ago that I don't recall the
messages and I've changed my python setup significantly since so recreating
won't be possible.
Was django used in 2.7? I don't recall seeing it before and I always used
the remote calls to peeringDB
Same here:
https://github.com/peeringdb/django-peeringdb/issues/37
"errors with django 3 so limit to django 2 or fix them #37"
Bill, if your issue is unique after review of:
https://github.com/peeringdb/django-peeringdb/issues
consider a new issue with details. The django 3 issue
The only issue I had was with django-peeringdb needing to use Django < 3.x. A
whole bunch of things don’t work with the latest version of the framework. I
had to put this requirement into my python projects that used the
django-peeringdb module and PY3.
Django<=2.2.9
> On Feb 11, 2020, at
Hi All,
Has anyone seen issues with the peeringDB python module when converting to
Python 3.x? I was unable to get the module working during my python 3
conversion as it seemed to require a localDB and no longer performed remote
calls properly. The documents seem a bit light.
This is not a