-
-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's new and readme: we are moving to Python 3.7 #9942
Conversation
Hi all, Comments from everyone who has worked on or commented on Python 3 are appreciated, especially from Reef, @jcsteh, and @LeonarddeR. Thanks, |
Hi, right, thanks for catching this, which also had a grammar problem (will resolve it once I wake up from sleep in the morning). Thanks.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can change the threshold release heading to 2019.3
Hi, I knew there was an issue about mentioning minor versions in docs – thanks for the link to the issue. Thanks.
|
Hi, Should we mention textUtils? Thanks. |
yes, sounds like a good idea. Probably best to point at examples from the changelog.
|
Hi, Regarding text utils, I have nothing to say - can't come up with a descriptive changelog for developers at the moment. Anything else from our PR pool? If not, I'll switch the PR to review mode. Thanks. |
How about something within the lines of:
|
Hi, Text utils: done. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking pretty good. Please update the description to cover which PR's (to threshold / threshold staging) have been covered by this. You can get most of the way there by copying entries from git log on the threshold branch. I suggest using the checkbox markdown:
- [ ] some PR not covered
- [x] some PR covered
Hi, I'll use git shortlog to edit the description. Thanks. |
Hi, To @LeonarddeR: whenever you are ready, please take a look at this PR. Thanks. |
Thanks @josephsl, I have updated the description so that they render as a checkboxes. It looks like there are still many PR's that need consideration. |
Hi, yes, including the just merged one (#9960). Thanks.
|
If no one volunteers before tomorrow (25-July 0600 UTC+0) , then I'll finish this off. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found two sentences where has should be have IMO. Could be wrong for the latter, though.
user_docs/en/changes.t2t
Outdated
- config.ConfigManager.getConfigValidationParameter is removed. A bug in getConfigValidation has been fixed in order for it being able to fully replace getConfigValidationParameter | ||
- inputCore.InputGesture.logIdentifier property has been removed. Now use inputCore.InputGesture.identifiers[0] instead. | ||
- textInfos.Point and textInfos.Rect has been removed and replaced by locationHelper.Point and locationHelper.RectLTRB, respectively. | ||
- braille.BrailleHandler._get/set_tether has been removed. Use getTether and setTether respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- braille.BrailleHandler._get/set_tether has been removed. Use getTether and setTether respectively. | |
- braille.BrailleHandler._get/set_tether have been removed. Use getTether and setTether respectively. |
Hi, I think part of that may have to do with subtle English grammar differences.
|
Hi, Let me at least commit the requested edits, and then I think we should decide our next steps. Thanks. |
I'd like to get this finished off and merged in, are you going to continue with it @josephsl? I don't think I will hold back threshold any longer. |
Hi, feel free to merge – let’s get the party started. Thanks.
|
Hi, Clarification: I'm done with this one. Thanks. |
@josephsl: could you please do a base branch switch for this? |
Because Appveyor changes Python x.y.z fromtime to time, it is bettre to just say Python x.y.
What's new entry suggested by Leonard de Ruijter (Babbage).
Reviewed by Leonard de Ruijter (Babbage): has -> have for two entries.
1cd5b05
to
fc7e441
Compare
Done. |
Should this be merged? |
Hi, when it is ready, yes. Thanks.
|
@derekriemer The checklist for PR's needs to be completed, I suspect many of these do not need an entry. This is on my list of things to do, but hasn't yet received priority. |
I have gone through the unchecked items and added entries. I also re-arranged the current items in the changes file. |
Link to issue number:
Gives closure to Upgrade NVDA codebase to Python 3 #7105
Summary of the issue:
What's new and readme still mentions Python 2.7, and in case of what's new, changes were needed.
Description of how this pull request fixes the issue:
Edits include mentioning Python 3.7 in both readme and what's new, as well as fixing things here and there in what's new/Threshold section. See the below section regarding work included in what's new and readme through this pull request and other Threshold work.
Testing performed:
None
Known issues with pull request:
Some parts are missing, such as filling in which issue introduced support for pyserial 3.4 and other things. What's new and readme are subject to change based on comments.
Change log entry:
None
Pull requests addressed by this work
Items with a checkmark are mentioned in what's new. Merge messages are ignored.
Speech refactor
Python 3.7
No entry necessary