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
Copy file name to clipboardExpand all lines: docs/backend/upgrading/version-specific-migration/upgrade-to-python3.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -305,16 +305,6 @@ These should be changed so that Python 3 is the default.
305
305
For example, string types (or text) should be represented as `'foo'`, not `u'foo'`, and bytes types (or data) should be represented as `b'bar'`, not `'bar'`.
306
306
Search for examples of `Py23DocChecker` in Plone's packages to find a pattern which allows updated doctests to pass in Python 2.
307
307
308
-
- To test your code against `buildout.coredev`, start by browsing to [Add-ons \[Jenkins\]](https://jenkins.plone.org/view/Add-ons/).
309
-
- Note there are jobs set up for Plone 4.3, 5.0, 5.1, and 5.2 on Python 2, and three jobs that run tests for Plone 5.2 on Python 3.6, Python 3.7, Python 3.8, and Python 3.9.
310
-
- Click the link {guilabel}`log in` on Jenkins website (top right).
311
-
For the first login, you must authorize Jenkins to have access to your GitHub account to authenticate.
312
-
- Click the link for the job you want to run.
313
-
For example, {guilabel}`Test add-on against Plone 5.2 on Python3.8`.
314
-
- Choose the link {guilabel}`Build with parameters` in the menu on the left-hand side.
315
-
- Fill the fields {guilabel}`ADDON_URL` and {guilabel}`ADDON_BRANCH` with your repository's URL and the branch name ("python3" if you followed these instructions).
316
-
- Start the build with the {guilabel}`Build` button.
0 commit comments