On 10/10/2019 7:20 am, 'Dimitri Maziuk' via Trac Users wrote:
On 10/9/19 2:06 PM, Jonathan Laufersweiler wrote:
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
Mickaël
You are a hero!
That means thank you very much. Your documentation skills are as amazing
as your dev-ops skills.
I struggle with both ...
Cheers
Mike
On 10/10/2019 12:20 am, Mickaël Bucas wrote:
Hi Mike
I encountered the same issue when I changed my system Python to
version 3.6,
On 10/10/2019 6:06 am, Jonathan Laufersweiler wrote:
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
Hi Mike
I encountered the same issue when I changed my system Python to
version 3.6, so I'm currently running Trac 1.2 in a virtualenv I've
created with the following commands :
--8<--
mkdir -p /var/lib/trac/$PROJECT/venv
virtualenv -p python2 /var/lib/trac/$PROJECT/venv
On 10/9/19 2:06 PM, Jonathan Laufersweiler wrote:
> 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
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
