[Meta] General feedback or comments regarding the Flask migration

[amercader]

This is a placeholder issue to make easier to discuss topics around the Pylons to Flask migration.

All details are written down on this wiki page:

https://github.com/ckan/ckan/wiki/Migration-from-Pylons-to-Flask

The main current working branch is poc-flask-views:

master...poc-flask-views

Some other proof of concept branches:

poc-flask-views...poc-flask-views.common-url_for-take-2
poc-flask-views.common-url_for-take-2...poc-flask-views.common-url_for-take-2-tests

[gamesbook]

Any idea on how long this may take? In terms of writing a new plug-in, should we just wait - or will there will be a guide to writing these in a way so as to make them "future proof"?

[TkTech]

From what I understand, effort is being made to not break plugins. You should be safe, and the majority of your logic will not change and only minor changes, such as to how your controller is laid out will need to be made.

[k-nut]

@gamesbook There is a pargraph in the wiki doc that talks about this and is likely to get updated when more information is available: What does this mean for my CKAN instance and/or extension?

[amercader]

@gamesbook This is likely to take a few months. Definitely don't hold back writing a new plugin, as there won't be massive changes needed when all the Flask work is merged. They will go along the lines described here. And this only if you use one of the affected interfaces:

https://github.com/ckan/ckan/wiki/Migration-from-Pylons-to-Flask#extensions-and-plugin-interfaces

[brylie]

I would like to help with this task. Is there any small, repetitive task that I can take as part of the larger Pylons to Flask migration? I am new to Flask, so something with a clear recipe that I can follow would be appreciated.

[cclauss]

Is this issue still open?

[tino097]

Flask migration completed