Skip to content
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

Tasks remaining to get to Python 3 #3333

Closed
74 of 77 tasks
cclauss opened this issue Apr 8, 2020 · 3 comments
Closed
74 of 77 tasks

Tasks remaining to get to Python 3 #3333

cclauss opened this issue Apr 8, 2020 · 3 comments
Assignees
Labels
Lead: @cclauss Issues overseen by Chris (Python3 & Dev-ops lead 2019-2021) [managed] Priority: 2 Important, as time permits. [managed] python Pull requests that update Python code Type: Bug Something isn't working. [managed] Type: Epic A feature or refactor that is big enough to require subissues. [managed]

Comments

@cclauss
Copy link
Contributor

cclauss commented Apr 8, 2020

Planning Doc

BOLD: Pull requests that are ready for review and merge.
ITALIC: Issues and PRs that are optional (nice-to-have).

@cclauss cclauss added Type: Bug Something isn't working. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Apr 8, 2020
@cclauss cclauss added this to the Active Sprint milestone Apr 9, 2020
@cclauss cclauss self-assigned this Apr 9, 2020
@tfmorris
Copy link
Contributor

tfmorris commented Apr 9, 2020

It seems like Infogami is going to be our biggest hurdle. Do we have a strategy for dealing with that?

@cclauss cclauss closed this as completed Apr 9, 2020
@cclauss cclauss reopened this Apr 9, 2020
@cclauss
Copy link
Contributor Author

cclauss commented Apr 9, 2020

Today Infogami appears to be our biggest hurdle but just a few months ago it was not.

Last year I was able to land many modernizations on Infogami so I have a fair understanding of that codebase. There are no miracles here so it will require effort but given the state of web.py (about to drop support for legacy Python) and OL (six files from pytests being green on Py3), I hope that it will be easier to get reviews on Infogami pull requests than it was at the end of 2019.

@xayhewalo xayhewalo added Lead: @cclauss Issues overseen by Chris (Python3 & Dev-ops lead 2019-2021) [managed] Priority: 2 Important, as time permits. [managed] Theme: Upgrade to Python 3 and removed Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Apr 15, 2020
@cclauss cclauss added the python label Apr 22, 2020
@cdrini cdrini modified the milestones: Active Sprint, Next (proposed) Sep 9, 2020
@cdrini cdrini modified the milestones: Active Sprint, Next (proposed) Oct 5, 2020
@cdrini cdrini modified the milestones: Next (proposed), Active Sprint Oct 30, 2020
@cclauss cclauss mentioned this issue Nov 1, 2020
3 tasks
@mekarpeles mekarpeles added the Type: Epic A feature or refactor that is big enough to require subissues. [managed] label Nov 18, 2020
@cclauss
Copy link
Contributor Author

cclauss commented Nov 23, 2020

Time to close this one! Thanks to everyone for helping to get us to Python 3!!

@mekarpeles mekarpeles added python Pull requests that update Python code and removed Module: Python labels Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @cclauss Issues overseen by Chris (Python3 & Dev-ops lead 2019-2021) [managed] Priority: 2 Important, as time permits. [managed] python Pull requests that update Python code Type: Bug Something isn't working. [managed] Type: Epic A feature or refactor that is big enough to require subissues. [managed]
Projects
None yet
Development

No branches or pull requests

5 participants