Important: please prepare to meet wxPython 4 and Python 3

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Important: please prepare to meet wxPython 4 and Python 3

Joseph Lee

Hi all,

 

Some of you may have heard of a wxPython project called “Phoenix”, a project to modernize wxPython codebase and make it compatible with Python 3. After several years of development, on April 16, 2017, wxPython Phoenix became widely available in the form of wxPython 4 alpha 1. With this development, the long-term goal of upgrading to Python 3 is closer at hand, as the only remaining dependency to be upgraded is SCons.

 

Many of you might be asking whether NVDA is functioning with wxPython 4 installed. I’m happy to announce that it is working to some extent. Although it is far from complete, I and others have laid the foundation for the community to start testing it in hopes of discovering bugs along the way. With this development, I also believe that it is time to start preparing our code (NVDA codebase, add-ons and others) to move to Python 3.

 

Relevant issues:

 

For add-on writers: I’d like to urge everyone to learn more about wxPython 4, including reading the migration guide, incompatible changes and so on. The biggest change is replacement of wx.PyDeadObjectError with RuntimeError. More importantly, I’d advise everyone to start preparing your code to handle Python 3 idioms such as Unicode strings, use of range function and what not (an excellent module to use is Six, which is also needed by wxPython 4).

 

Thank you.

Cheers,

Joseph


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Important: please prepare to meet wxPython 4 andPython 3

Brian's Mail list account BY
Hi, its interesting though, don't you think that many programs are  not
going the Python 3 route since the code is not documented well enough to
make it an easy thing to do with bugs  surfacing all over the place.
 What really is the advantage for the end user to updating to these new
constructs?
 Is it that eventually the old libraries will no longer work in some way? If
not then why bother? Playing devils advocate here as somebody had to ask,
and I decided it was  going to be me!
 Brian

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <[hidden email]>
To: "'NVDA screen reader development'" <[hidden email]>
Sent: Wednesday, April 26, 2017 3:18 AM
Subject: [Nvda-devel] Important: please prepare to meet wxPython 4 andPython
3


> Hi all,
>
>
>
> Some of you may have heard of a wxPython project called "Phoenix", a
> project
> to modernize wxPython codebase and make it compatible with Python 3. After
> several years of development, on April 16, 2017, wxPython Phoenix became
> widely available in the form of wxPython 4 alpha 1. With this development,
> the long-term goal of upgrading to Python 3 is closer at hand, as the only
> remaining dependency to be upgraded is SCons.
>
>
>
> Many of you might be asking whether NVDA is functioning with wxPython 4
> installed. I'm happy to announce that it is working to some extent.
> Although
> it is far from complete, I and others have laid the foundation for the
> community to start testing it in hopes of discovering bugs along the way.
> With this development, I also believe that it is time to start preparing
> our
> code (NVDA codebase, add-ons and others) to move to Python 3.
>
>
>
> Relevant issues:
>
> * wxPython 4.0.0: https://github.com/nvaccess/nvda/issues/7077
> * wxPython 4 pull request:
> https://github.com/nvaccess/nvda/issues/7104
> * Upgrade to Python 3: https://github.com/nvaccess/nvda/issues/7105
>
>
>
> For add-on writers: I'd like to urge everyone to learn more about wxPython
> 4, including reading the migration guide, incompatible changes and so on.
> The biggest change is replacement of wx.PyDeadObjectError with
> RuntimeError.
> More importantly, I'd advise everyone to start preparing your code to
> handle
> Python 3 idioms such as Unicode strings, use of range function and what
> not
> (an excellent module to use is Six, which is also needed by wxPython 4).
>
>
>
> Thank you.
>
> Cheers,
>
> Joseph
>
>


--------------------------------------------------------------------------------


> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot


--------------------------------------------------------------------------------


> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Important: please prepare to meet wxPython 4 andPython 3

James Teh
The real transition to Python 3 won't happen for some time yet. Beyond wxPython, I suspect we won't be doing any Python 3 related work until at least next year. Still, it's worth thinking about when writing new code, major changes, etc.

Having said that, Python 2.7 is end-of-life in 2020. So, we must transition before then (and must thus begin the process quite some time before that). It's also worth noting that the latest Python 3 release does not support Windows XP, so we'll definitely lose XP support in 2020, if not earlier. This is one of those non-negotiables: it is paramount that we are working with a "supported" version of Python.

Sent from a mobile device

> On 26 Apr 2017, at 6:24 pm, Brian's Mail list account BY <[hidden email]> wrote:
>
> Hi, its interesting though, don't you think that many programs are  not
> going the Python 3 route since the code is not documented well enough to
> make it an easy thing to do with bugs  surfacing all over the place.
> What really is the advantage for the end user to updating to these new
> constructs?
> Is it that eventually the old libraries will no longer work in some way? If
> not then why bother? Playing devils advocate here as somebody had to ask,
> and I decided it was  going to be me!
> Brian
>
> [hidden email]
> Sent via blueyonder.
> Please address personal email to:-
> [hidden email], putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Joseph Lee" <[hidden email]>
> To: "'NVDA screen reader development'" <[hidden email]>
> Sent: Wednesday, April 26, 2017 3:18 AM
> Subject: [Nvda-devel] Important: please prepare to meet wxPython 4 andPython
> 3
>
>
>> Hi all,
>>
>>
>>
>> Some of you may have heard of a wxPython project called "Phoenix", a
>> project
>> to modernize wxPython codebase and make it compatible with Python 3. After
>> several years of development, on April 16, 2017, wxPython Phoenix became
>> widely available in the form of wxPython 4 alpha 1. With this development,
>> the long-term goal of upgrading to Python 3 is closer at hand, as the only
>> remaining dependency to be upgraded is SCons.
>>
>>
>>
>> Many of you might be asking whether NVDA is functioning with wxPython 4
>> installed. I'm happy to announce that it is working to some extent.
>> Although
>> it is far from complete, I and others have laid the foundation for the
>> community to start testing it in hopes of discovering bugs along the way.
>> With this development, I also believe that it is time to start preparing
>> our
>> code (NVDA codebase, add-ons and others) to move to Python 3.
>>
>>
>>
>> Relevant issues:
>>
>> * wxPython 4.0.0: https://github.com/nvaccess/nvda/issues/7077
>> * wxPython 4 pull request:
>> https://github.com/nvaccess/nvda/issues/7104
>> * Upgrade to Python 3: https://github.com/nvaccess/nvda/issues/7105
>>
>>
>>
>> For add-on writers: I'd like to urge everyone to learn more about wxPython
>> 4, including reading the migration guide, incompatible changes and so on.
>> The biggest change is replacement of wx.PyDeadObjectError with
>> RuntimeError.
>> More importantly, I'd advise everyone to start preparing your code to
>> handle
>> Python 3 idioms such as Unicode strings, use of range function and what
>> not
>> (an excellent module to use is Six, which is also needed by wxPython 4).
>>
>>
>>
>> Thank you.
>>
>> Cheers,
>>
>> Joseph
>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> --------------------------------------------------------------------------------
>
>
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Important: please prepare to meet wxPython 4andPython 3

Brian Gaff Lineone downstairs
Yes well then Hopefully by 2020, we shall see all the  XP Machines at least
in our health service replaced at last as I think the last time they asked
Microsoft to give them even longer support they declined to provide it and I
would suggest that the current functions of nvda in XP are pretty muchall
one needs given that new software cannot run on  xp, such as Dropbox PDF
reader and many more.
 I'll probably run my couple of machines into the ground as back up and
printer servers etc, but they are getting almost unusable these days due to
changes in the web etc.
 Sad to see it go, but there you are.
 I still prefer 7 to 10 though, I have to say.
 Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[hidden email]>
To: "NVDA screen reader development" <[hidden email]>
Sent: Wednesday, April 26, 2017 10:09 AM
Subject: Re: [Nvda-devel] Important: please prepare to meet wxPython
4andPython 3


> The real transition to Python 3 won't happen for some time yet. Beyond
> wxPython, I suspect we won't be doing any Python 3 related work until at
> least next year. Still, it's worth thinking about when writing new code,
> major changes, etc.
>
> Having said that, Python 2.7 is end-of-life in 2020. So, we must
> transition before then (and must thus begin the process quite some time
> before that). It's also worth noting that the latest Python 3 release does
> not support Windows XP, so we'll definitely lose XP support in 2020, if
> not earlier. This is one of those non-negotiables: it is paramount that we
> are working with a "supported" version of Python.
>
> Sent from a mobile device
>
>> On 26 Apr 2017, at 6:24 pm, Brian's Mail list account BY
>> <[hidden email]> wrote:
>>
>> Hi, its interesting though, don't you think that many programs are  not
>> going the Python 3 route since the code is not documented well enough to
>> make it an easy thing to do with bugs  surfacing all over the place.
>> What really is the advantage for the end user to updating to these new
>> constructs?
>> Is it that eventually the old libraries will no longer work in some way?
>> If
>> not then why bother? Playing devils advocate here as somebody had to ask,
>> and I decided it was  going to be me!
>> Brian
>>
>> [hidden email]
>> Sent via blueyonder.
>> Please address personal email to:-
>> [hidden email], putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Joseph Lee" <[hidden email]>
>> To: "'NVDA screen reader development'" <[hidden email]>
>> Sent: Wednesday, April 26, 2017 3:18 AM
>> Subject: [Nvda-devel] Important: please prepare to meet wxPython 4
>> andPython
>> 3
>>
>>
>>> Hi all,
>>>
>>>
>>>
>>> Some of you may have heard of a wxPython project called "Phoenix", a
>>> project
>>> to modernize wxPython codebase and make it compatible with Python 3.
>>> After
>>> several years of development, on April 16, 2017, wxPython Phoenix became
>>> widely available in the form of wxPython 4 alpha 1. With this
>>> development,
>>> the long-term goal of upgrading to Python 3 is closer at hand, as the
>>> only
>>> remaining dependency to be upgraded is SCons.
>>>
>>>
>>>
>>> Many of you might be asking whether NVDA is functioning with wxPython 4
>>> installed. I'm happy to announce that it is working to some extent.
>>> Although
>>> it is far from complete, I and others have laid the foundation for the
>>> community to start testing it in hopes of discovering bugs along the
>>> way.
>>> With this development, I also believe that it is time to start preparing
>>> our
>>> code (NVDA codebase, add-ons and others) to move to Python 3.
>>>
>>>
>>>
>>> Relevant issues:
>>>
>>> * wxPython 4.0.0: https://github.com/nvaccess/nvda/issues/7077
>>> * wxPython 4 pull request:
>>> https://github.com/nvaccess/nvda/issues/7104
>>> * Upgrade to Python 3: https://github.com/nvaccess/nvda/issues/7105
>>>
>>>
>>>
>>> For add-on writers: I'd like to urge everyone to learn more about
>>> wxPython
>>> 4, including reading the migration guide, incompatible changes and so
>>> on.
>>> The biggest change is replacement of wx.PyDeadObjectError with
>>> RuntimeError.
>>> More importantly, I'd advise everyone to start preparing your code to
>>> handle
>>> Python 3 idioms such as Unicode strings, use of range function and what
>>> not
>>> (an excellent module to use is Six, which is also needed by wxPython 4).
>>>
>>>
>>>
>>> Thank you.
>>>
>>> Cheers,
>>>
>>> Joseph
>>>
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Important: please prepare to meet wxPython 4andPython 3

Brian's Mail list account BY
In reply to this post by James Teh
Yes well then Hopefully by 2020, we shall see all the  XP Machines at least
in our health service replaced at last as I think the last time they asked
Microsoft to give them even longer support they declined to provide it and I
would suggest that the current functions of nvda in XP are pretty muchall
one needs given that new software cannot run on  xp, such as Dropbox PDF
reader and many more.
 I'll probably run my couple of machines into the ground as back up and
printer servers etc, but they are getting almost unusable these days due to
changes in the web etc.
 Sad to see it go, but there you are.
 I still prefer 7 to 10 though, I have to say.
 Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[hidden email]>
To: "NVDA screen reader development" <[hidden email]>
Sent: Wednesday, April 26, 2017 10:09 AM
Subject: Re: [Nvda-devel] Important: please prepare to meet wxPython
4andPython 3


> The real transition to Python 3 won't happen for some time yet. Beyond
> wxPython, I suspect we won't be doing any Python 3 related work until at
> least next year. Still, it's worth thinking about when writing new code,
> major changes, etc.
>
> Having said that, Python 2.7 is end-of-life in 2020. So, we must
> transition before then (and must thus begin the process quite some time
> before that). It's also worth noting that the latest Python 3 release does
> not support Windows XP, so we'll definitely lose XP support in 2020, if
> not earlier. This is one of those non-negotiables: it is paramount that we
> are working with a "supported" version of Python.
>
> Sent from a mobile device
>
>> On 26 Apr 2017, at 6:24 pm, Brian's Mail list account BY
>> <[hidden email]> wrote:
>>
>> Hi, its interesting though, don't you think that many programs are  not
>> going the Python 3 route since the code is not documented well enough to
>> make it an easy thing to do with bugs  surfacing all over the place.
>> What really is the advantage for the end user to updating to these new
>> constructs?
>> Is it that eventually the old libraries will no longer work in some way?
>> If
>> not then why bother? Playing devils advocate here as somebody had to ask,
>> and I decided it was  going to be me!
>> Brian
>>
>> [hidden email]
>> Sent via blueyonder.
>> Please address personal email to:-
>> [hidden email], putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Joseph Lee" <[hidden email]>
>> To: "'NVDA screen reader development'" <[hidden email]>
>> Sent: Wednesday, April 26, 2017 3:18 AM
>> Subject: [Nvda-devel] Important: please prepare to meet wxPython 4
>> andPython
>> 3
>>
>>
>>> Hi all,
>>>
>>>
>>>
>>> Some of you may have heard of a wxPython project called "Phoenix", a
>>> project
>>> to modernize wxPython codebase and make it compatible with Python 3.
>>> After
>>> several years of development, on April 16, 2017, wxPython Phoenix became
>>> widely available in the form of wxPython 4 alpha 1. With this
>>> development,
>>> the long-term goal of upgrading to Python 3 is closer at hand, as the
>>> only
>>> remaining dependency to be upgraded is SCons.
>>>
>>>
>>>
>>> Many of you might be asking whether NVDA is functioning with wxPython 4
>>> installed. I'm happy to announce that it is working to some extent.
>>> Although
>>> it is far from complete, I and others have laid the foundation for the
>>> community to start testing it in hopes of discovering bugs along the
>>> way.
>>> With this development, I also believe that it is time to start preparing
>>> our
>>> code (NVDA codebase, add-ons and others) to move to Python 3.
>>>
>>>
>>>
>>> Relevant issues:
>>>
>>> * wxPython 4.0.0: https://github.com/nvaccess/nvda/issues/7077
>>> * wxPython 4 pull request:
>>> https://github.com/nvaccess/nvda/issues/7104
>>> * Upgrade to Python 3: https://github.com/nvaccess/nvda/issues/7105
>>>
>>>
>>>
>>> For add-on writers: I'd like to urge everyone to learn more about
>>> wxPython
>>> 4, including reading the migration guide, incompatible changes and so
>>> on.
>>> The biggest change is replacement of wx.PyDeadObjectError with
>>> RuntimeError.
>>> More importantly, I'd advise everyone to start preparing your code to
>>> handle
>>> Python 3 idioms such as Unicode strings, use of range function and what
>>> not
>>> (an excellent module to use is Six, which is also needed by wxPython 4).
>>>
>>>
>>>
>>> Thank you.
>>>
>>> Cheers,
>>>
>>> Joseph
>>>
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "James Teh" <[hidden email]>
To: "NVDA screen reader development" <[hidden email]>
Sent: Wednesday, April 26, 2017 10:09 AM
Subject: Re: [Nvda-devel] Important: please prepare to meet wxPython
4andPython 3


> The real transition to Python 3 won't happen for some time yet. Beyond
> wxPython, I suspect we won't be doing any Python 3 related work until at
> least next year. Still, it's worth thinking about when writing new code,
> major changes, etc.
>
> Having said that, Python 2.7 is end-of-life in 2020. So, we must
> transition before then (and must thus begin the process quite some time
> before that). It's also worth noting that the latest Python 3 release does
> not support Windows XP, so we'll definitely lose XP support in 2020, if
> not earlier. This is one of those non-negotiables: it is paramount that we
> are working with a "supported" version of Python.
>
> Sent from a mobile device
>
>> On 26 Apr 2017, at 6:24 pm, Brian's Mail list account BY
>> <[hidden email]> wrote:
>>
>> Hi, its interesting though, don't you think that many programs are  not
>> going the Python 3 route since the code is not documented well enough to
>> make it an easy thing to do with bugs  surfacing all over the place.
>> What really is the advantage for the end user to updating to these new
>> constructs?
>> Is it that eventually the old libraries will no longer work in some way?
>> If
>> not then why bother? Playing devils advocate here as somebody had to ask,
>> and I decided it was  going to be me!
>> Brian
>>
>> [hidden email]
>> Sent via blueyonder.
>> Please address personal email to:-
>> [hidden email], putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Joseph Lee" <[hidden email]>
>> To: "'NVDA screen reader development'" <[hidden email]>
>> Sent: Wednesday, April 26, 2017 3:18 AM
>> Subject: [Nvda-devel] Important: please prepare to meet wxPython 4
>> andPython
>> 3
>>
>>
>>> Hi all,
>>>
>>>
>>>
>>> Some of you may have heard of a wxPython project called "Phoenix", a
>>> project
>>> to modernize wxPython codebase and make it compatible with Python 3.
>>> After
>>> several years of development, on April 16, 2017, wxPython Phoenix became
>>> widely available in the form of wxPython 4 alpha 1. With this
>>> development,
>>> the long-term goal of upgrading to Python 3 is closer at hand, as the
>>> only
>>> remaining dependency to be upgraded is SCons.
>>>
>>>
>>>
>>> Many of you might be asking whether NVDA is functioning with wxPython 4
>>> installed. I'm happy to announce that it is working to some extent.
>>> Although
>>> it is far from complete, I and others have laid the foundation for the
>>> community to start testing it in hopes of discovering bugs along the
>>> way.
>>> With this development, I also believe that it is time to start preparing
>>> our
>>> code (NVDA codebase, add-ons and others) to move to Python 3.
>>>
>>>
>>>
>>> Relevant issues:
>>>
>>> * wxPython 4.0.0: https://github.com/nvaccess/nvda/issues/7077
>>> * wxPython 4 pull request:
>>> https://github.com/nvaccess/nvda/issues/7104
>>> * Upgrade to Python 3: https://github.com/nvaccess/nvda/issues/7105
>>>
>>>
>>>
>>> For add-on writers: I'd like to urge everyone to learn more about
>>> wxPython
>>> 4, including reading the migration guide, incompatible changes and so
>>> on.
>>> The biggest change is replacement of wx.PyDeadObjectError with
>>> RuntimeError.
>>> More importantly, I'd advise everyone to start preparing your code to
>>> handle
>>> Python 3 idioms such as Unicode strings, use of range function and what
>>> not
>>> (an excellent module to use is Six, which is also needed by wxPython 4).
>>>
>>>
>>>
>>> Thank you.
>>>
>>> Cheers,
>>>
>>> Joseph
>>>
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel