-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Trac 1.4.x #105
Comments
I'd really like to upgrade, but I think this might get hard because 1.4.x does not seem to allow an easy way to override templates: https://trac.edgewall.org/browser/branches/1.4-stable/trac/web/chrome.py#L1386 This currently puts the default trac templates first in the list, which prevents overriding as far as I can see. In trunk it puts the templates dir from the env first: https://trac.edgewall.org/browser/trunk/trac/web/chrome.py#L745 |
Since 1.6 will be python 3 only, I'd really like to go via 1.4 first. I wonder if it makes sense to fork trac and fix the few things that needs fixing… |
Okay, so I started working on this locally. First and foremost there is one problem: We have some views in there that are requested from the tracdb app in djangoproject.com. We need to rewrite those in a way to be compatible first. Working on it. |
I've taken @apollo13 's work from #146 and added a few more fixes: #146 I believe Florian's comments about Trac seems to finally have a Python3-compatible version, so once this is merged, I would like to try to finally upgrade from Python 2.7 (and Django 1.11) to something a bit less ancient 🦕 |
Fixed in #146 Good work everyone! 🚀 |
Nicely done, thank you Baptiste!
…On Wed, Jan 24, 2024, at 22:00, Baptiste Mispelon wrote:
Fixed in #146
<#146> Good work
everyone! 🚀
—
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAT5C3N2VE3FIPX4CKYMCDYQFY6PAVCNFSM4UWOCK3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJQHA4TANJZHAZQ>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
See release notes.
The text was updated successfully, but these errors were encountered: