Topics

Request for comments on add-on updating and python 3: create a dedicated "-py3" keys on add-ons website?

 

Dear NVDA developers and add-on authors,

 

A few days ago an NV Access staff hinted at a major announcement regarding Python 3 transition work, and most of you may remember my own set of source code level snapshots powered by Python 3. Thus the following RFC (request for comments):

 

At the moment the community add-on site uses an internal data structure for hosting add-on files and installer URL’s referenced by keys, with different keys pointing to different update channels for some add-ons. Given that some add-on authors have looked into porting their add-ons to Python 3 (and some add-ons are compatible with Python 3), I would like to propose creating a set of keys that denote Python 3 version of add-ons. For example, Windows 10 App Essentials is represented by “w10”, and a Python 3 version would be referenced under “w10-py3” key.

 

The biggest advantage is separation of Python 2 and 3 versions of an add-on. This allows developers and users to compare differences between two versions of an add-on. The downside is possible confusion as to which one is which, along with a possibility of people referencing Python 2 version of the add-on under Python 3 key and vice versa.

 

Constraints and issues:

 

  1. Python 3 transition schedule should be established by NV Access.
  2. Not all add-ons were ported to Python 3 mode, including some considered important for the NVDA community (speech synthesizers, for instance).

 

Comments are appreciated. Thanks.

Cheers,

Joseph

Brian's Mail list account
 

Is it possible under the construct to actually make add ons that are running on the wrong version of python, not actually run in either direction?


Another thing I meant to ask elsewhere is this. If python 3 version of nvda comes out..
1. Should it work on windows 7
2. what is its policy toward already existing add ons etc, or would it tend to be installed completely stand alone in a different folder and the shrotcut merely changed to the new place so if there were issues a user simply recreates the old shortcut and stops it autorunning at start up.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Saturday, March 30, 2019 2:10 AM
Subject: [nvda-devel] Request for comments on add-on updating and python 3: create a dedicated "-py3" keys on add-ons website?


Dear NVDA developers and add-on authors,



A few days ago an NV Access staff hinted at a major announcement regarding
Python 3 transition work, and most of you may remember my own set of source
code level snapshots powered by Python 3. Thus the following RFC (request
for comments):



At the moment the community add-on site uses an internal data structure for
hosting add-on files and installer URL's referenced by keys, with different
keys pointing to different update channels for some add-ons. Given that some
add-on authors have looked into porting their add-ons to Python 3 (and some
add-ons are compatible with Python 3), I would like to propose creating a
set of keys that denote Python 3 version of add-ons. For example, Windows 10
App Essentials is represented by "w10", and a Python 3 version would be
referenced under "w10-py3" key.



The biggest advantage is separation of Python 2 and 3 versions of an add-on.
This allows developers and users to compare differences between two versions
of an add-on. The downside is possible confusion as to which one is which,
along with a possibility of people referencing Python 2 version of the
add-on under Python 3 key and vice versa.



Constraints and issues:



1. Python 3 transition schedule should be established by NV Access.
2. Not all add-ons were ported to Python 3 mode, including some
considered important for the NVDA community (speech synthesizers, for
instance).



Comments are appreciated. Thanks.

Cheers,

Joseph