You're right that we should move to python3 first.
Beside other stuff to do: I mentioned befor that i am working on the tabbed pages, but adding a GDPR took precedence over tabbed pages. So my personal tasks are:
- Make the needed change for full filling the GDPR
- Add the tabbed pages ( the branch is nearly close to ready)
- Work on other stuff, e.g. porting to python3
But every help for porting to Python 3 is appreciated
And I know that it is not the best idea, but enabling DEBUG=True probably will help somebody like me to track down bugs .
That's a no go, even on the alpha site. Better create your own copy of the website locally This can also be done on windows.
And also we can make a simple functional test list. What we should do, what we should expect. Something like:
For sure I can help with writing down this tests and then doing them on test instance. That would help with upgrading to other django & packages upgrades.
I am not very familiar with tests. My imagination to 'fabricate' possible culprits is quite small, so i am in favor of testing manually. Or do i misunderstand your proposal?
The way i would try to port to Python 3 is on an per app basis: Create a branch which only consist e.g. of the mainpage and start to port the main view and test it, then add another app (e.g. news) to the branch and port it to Python3, test it, then the wiki and test, and so on.
But thats worth another topic, or better handling this questions in the bugtracker on launchpad.
Back to the topic:
My suggestion is not that difficult to implement, IMHO, so i would vote for it