You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Issue #15886 raises the problem of python environment maintenance between nvda core & add-ons. How much responsibility does NV Access take to provide the environment that add-on developers need to build their code, and thus avoid the developer having to roll their own and coming up against version incompatibilities, dependency chain issues, architecture compatibility issues, etc.
In order for NV Access to manage this issue more effectively, a first step is to clearly list the Python standard library modules included in nvda's binary builds.
Describe the solution you'd like
In the build system, after building NVDA with scons, recursively find all *.pyc files in the generated library.zip
Write them all to a file, converting their paths to Python module syntax, I.e. from x\y\z.pyc to x.y.z.
Make sure that file is exported as an artifact.
Then at a later stage, we can look at producing diffs of this file between releases.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
seanbudd
added
p5
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
triaged
Has been triaged, issue is waiting for implementation.
labels
Jan 1, 2024
Is your feature request related to a problem? Please describe.
Issue #15886 raises the problem of python environment maintenance between nvda core & add-ons. How much responsibility does NV Access take to provide the environment that add-on developers need to build their code, and thus avoid the developer having to roll their own and coming up against version incompatibilities, dependency chain issues, architecture compatibility issues, etc.
In order for NV Access to manage this issue more effectively, a first step is to clearly list the Python standard library modules included in nvda's binary builds.
Describe the solution you'd like
Then at a later stage, we can look at producing diffs of this file between releases.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: