Another option would be to use PyInstaller to package up a minimal 2.7 interpreter with the bytecode for Trac and its dependencies into a into a stand-alone executable package. This would make updating Trac more of a chore, but would simplify the service & routing setup compared to the venv approach. YMMV, of course. --JonL
On Tuesday, October 8, 2019 at 10:04:32 PM UTC-5, Mike Dewhirst wrote: > > I had to stop using Trac when I upgraded the machine to Python3. Call > that machine pq3 and Trac is currently off the air. > > The reason is pq3 also runs a couple of Django staging servers which > have moved beyond version 1.11 and are therefore no longer capable of > running on Python 2.7. > > I can't wait for Trac on Python3 so I think my choices are ... > > 1. Set up a Python 2.7 venv on pq3 and re-install Trac there > > ... OR install Python 2.7 on a separate machine - call it pq2 - and ... > > 2. Redirect Trac traffic to pq2 from pq3 using Apache redirection > > 3. Redirect Trac traffic to pq2 from the router using different port > forwarding - say 4430 > > pq2 and pq3 are both Ubuntu 18.04 and Apache 2.4 on both. Both machines > are behind the same router and I can only direct web traffic to one and > that has to be pq3. The Trac database is on pq3. > > What do you recommend is the easiest course? > > I plan to adopt Trac for Python3 as soon as it is released and retire > pq2 permanently. > > Thanks for any advice. > > Cheers > > Mike > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/02acdc83-8b3f-4763-adca-114f224fe7d6%40googlegroups.com.
