The release got paused a bit ago, after I discovered some LGPL packages in our
requirements.txt file which the ASF doesn't permit to be included in a project.
Work has been completed to make them optional
https://forge-allura.apache.org/p/allura/tickets/8386/
So now I'm back to thinking about making the next Allura release very soon.
There is also a big merge request
https://forge-allura.apache.org/p/allura/git/merge-requests/350/ pending. I
think its probably close to ready, but I really want to get an Allura release
ready. So that new feature can land in the following release I guess.
Ingo - what issues did you have with python 3.8? I haven't tried 3.8 with any
big projects yet. And I was hoping that once we drop python2 we could start
supporting two or more 3.x versions simultaneously. So people have a little
flexibility when installing/upgrading.
Any additional thoughts before I proceed with the release?
On 3/4/21 12:43 PM, Ingo Hornberger wrote:
Hi Dave,
I fully agree with you. Having one release, bridging the move between py2
and py3 should be more than enough for most users.
Heavy adaptations, like Vehicle Forge, or such, might have more problems to
port their stuff. But as you said: py2 is dead already!
Personally I experienced a lot of compatibility problems in our internal
python tools, starting with Python 3.8. So I would propose to officially
support only one specific py3 version. This could currently be 3.7.
Cheers,
Ingo
Dave Brondsema <d...@brondsema.net> schrieb am Do., 4. März 2021, 00:38:
On 3/3/21 6:36 PM, Dave Brondsema wrote:
It's been well over a year since the last Allura release, I can prepare
the next
one soon, but wanted to discuss what versions of python we support.
Python 3 support has been added over the past year. Specifically Allura
should
work on python 3.6 and 3.7. I haven't tested 3.5 but that's not too
common of a
release I think. Python 3.8 and beyond will need additional changes to
support,
but shouldn't be too difficult.
Python 2 is still fully supported in Allura right now, so this release
will be a
good bridging step for anyone updating their python versions. How long
should
we support Python 2? It is end-of-life over a year now, but I know OS
distributions and larger organizations can take longer to upgrade. Is
anyone
running Allura where they can't switch to Python 3.6+?
I would suggest that this be the only release of Allura to support both
python 2
& 3. The following release could start dropping python 2 support, which
will
make it easier to move forward with python 3.8 and 3.9. And make the
code
simpler and cleaner.
I forgot to add that one bit of code still on python 2 is the mod_python
ApacheAccessHandler.py used for hosting code repos and doing permission
checks
on them. That is separate from the main Allura codebase, so I don't think
that's a blocker. Ingo and I have been discussing options on
https://forge-allura.apache.org/p/allura/tickets/8352/ since its not real
clear
how to proceed yet.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
