I know the last deluge releason targets python 3.6, and 2.2 was intended to be 3.7 (which is now also EOL)
Is there anything blocking just bumping the minimum to 3.8 or even 3.9?
Bumping minimum python version?
Re: Bumping minimum python version?
I'm on the develop branch running from source, and using 3.10 - so I do not think so.
Just be aware of the potential for plugins needing it removed from their filename and what packages are upgraded if you run into any errors.
Just be aware of the potential for plugins needing it removed from their filename and what packages are upgraded if you run into any errors.
-
- Member
- Posts: 20
- Joined: Sun Dec 22, 2019 4:24 pm
Re: Bumping minimum python version?
I'm working on a PR to move the plug-ins to wheels using importlib
Re: Bumping minimum python version?
Broad OS support for users means we target the oldest Python in use so just because it's eol doesn't mean we should jump version too quickly. However we should jump to minimum 3.8 considering 3.7 status.
Re: Bumping minimum python version?
Using wheels is an interesting concept, I had major issues with trying to move plugins away from eggs so keen to see how you are tackling since they need to be unpacked and installed.
If we really need to, we can vendor a library in the package.
If we really need to, we can vendor a library in the package.
-
- Member
- Posts: 20
- Joined: Sun Dec 22, 2019 4:24 pm
Re: Bumping minimum python version?
Thing is, I managed to make them work without unpacking them. Vendoring libraries likely won't be needed since we can use importlib_resources and importib_metadata.
Most of the work is done, I'm currently in the process of ironing out some kinks and writing some tests
Most of the work is done, I'm currently in the process of ironing out some kinks and writing some tests