This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
ckanext-datagovtheme Py3 + CKAN 2.9 support #567
Milestone
Comments
adborden
changed the title
Add ckanext-datagovtheme to CKAN 2.9
ckanext-datagovtheme Py3 + CKAN 2.9 support
May 3, 2021
14 tasks
caniusepython3:
|
|
Some hacks and work arounds we should come back to address:
|
Waiting on James' return to finish the review and close out the issue. |
This was referenced May 27, 2021
Not sure if this effects anything, but on the main branch, there is still one pip package that isn't python 3 supported?
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
User Story
As a data.gov developer, I want ckanext-datagovtheme running with CKAN 2.9 and Python 3 so that we can move out of CKAN 2.8 and reduce our technical debt and meet compliance standards.
Acceptance Criteria
THEN I see a successful job testing the extension under CKAN 2.9
AND I see a successful job testing the extension under CKAN 2.8
AND I see a successful job testing the extension under the legacy test environment
THEN I see CI fail due to test coverage being below a threshold
Background
CKAN 2.9 extension tracker.
Details / tasks
The goal is to support running this extension against CKAN 2.9 (Python 3) and CKAN 2.8 (Python 2) environments.
Please refer to the main CKAN documentation for Python 3 extensions migration. We're not following this guide exactly. Instead of creating a long-lived py3 branch, we should be merging often. New CI test suites don't need to required or to be fully passing in order to merge. It's only important that changes don't introduce new failures or break the existing test suites.
Below are a list of tasks. Depending on the extension's functionality, not all tasks will be actionable.
Tasks:
main
.check_ckan_version
caniusepython3 -r requirements.txt
from within the virtualenv) and post the results to this issue (docs)tests
dir totests/nose
in order to preserve existing test environment (example)futurize --both-stages --write ckanext
git grep -w 'paste\|pylons'
should return no imports) (docs)controller='package'
->controller='dataset'
orcontroller='resource'
Additional resources:
The text was updated successfully, but these errors were encountered: