Allura and Python3

[Ingo Hornberger <in...@gmx.net>]

Hi!
Are there any plans of making a new release to support python3?
I did a test, and ported our web page (forge.codesys.com) to python3 and to
the allura master branch.

Here is my experience:
- Error messages were not very straight forward. So I reviewed many commits
from Dave to get an idea what needs to be changed.
- The changes, necessary in the Ini-File, were hard to find.
- Luckily I knew, that I need to use "pip instal -e ." instead of calling
setup.py from watching the tickets
- I needed to find out how the new virtualenv had to be setup (changes, in
init-docker-dev.sh - where I obviously have my own one)

The rest of the work was just porting my own extensions to python3, and
updating the docker images. So far it looks pretty good, and I'd love to
plan the switch to the new release. So I am curious about your plans.

And finally, thanks for the great work, upgrading allura to python3. This
was a really important step!

Best regards,
Ingo

Re: Allura and Python3

[Dave Brondsema <da...@brondsema.net>]

Hi,

Yes we do need to make a release of Allura before too much longer.  It's been 
over a year since our last release!

I think python 3 support is more-or-less ready.  I would like to set up Jenkins 
to run with python 3, and at my company we have some internal extensions to do 
more testing with (which could show some core Allura things that need to be 
fixed still).

Its very encouraging to hear that you were able to use python3 on latest master, 
and upgrade your environment & custom code.  Thanks for sharing your feedback, 
that will be helpful when we write up the next release notes.

And then at some point later we'll need to discuss when to drop python 2 support :)

-Dave

On 12/7/20 4:34 PM, Ingo Hornberger wrote:
> Hi!
> Are there any plans of making a new release to support python3?
> I did a test, and ported our web page (forge.codesys.com) to python3 and to
> the allura master branch.
> 
> Here is my experience:
> - Error messages were not very straight forward. So I reviewed many commits
> from Dave to get an idea what needs to be changed.
> - The changes, necessary in the Ini-File, were hard to find.
> - Luckily I knew, that I need to use "pip instal -e ." instead of calling
> setup.py from watching the tickets
> - I needed to find out how the new virtualenv had to be setup (changes, in
> init-docker-dev.sh - where I obviously have my own one)
> 
> The rest of the work was just porting my own extensions to python3, and
> updating the docker images. So far it looks pretty good, and I'd love to
> plan the switch to the new release. So I am curious about your plans.
> 
> And finally, thanks for the great work, upgrading allura to python3. This
> was a really important step!
> 
> Best regards,
> Ingo
> 


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
               <><