Hello. Thanks for django-windows-tools - it's been really useful. We've upgraded our systems to python 3 and had to make some changes to the module to get that working. Hopefully this is useful for you!
There are a few things we're still not sure about:
If you can find some supporting evidence which suggests that FCGI parameter keywords and values are always pure ASCII then some of the encoding work can be removed.
We've re-enabled the cgitb feature but have observed what look like exception loops in some circumstances which end up with an FCGI timeout. We've mitigated this by ensuring that the backtrace is written to the fcgi log file but if the timeout could be fixed that would be better (obviously). It would be a shame to lose the cgitb.
The changes we've made appear to be backwards compatible to python 2.7. I'm not sure how much further back they will work.
When the FCGIServer's run method opens stdin and stdout (or possibly stdin and stdin again??) We're not certain whether the call to msvcrt.setmode is still required.
Let us know if you'd like us to do more work on this feature.
Hello. Thanks for django-windows-tools - it's been really useful. We've upgraded our systems to python 3 and had to make some changes to the module to get that working. Hopefully this is useful for you!
There are a few things we're still not sure about:
Let us know if you'd like us to do more work on this feature.
Kind regards,
Chris Eveleigh Abide Financial