-
Notifications
You must be signed in to change notification settings - Fork 117
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
Backport master to 4.4 #574
Conversation
* added ncml to supported formats * added ncml schema
* removed PY2 usage * removed flufl.enum * removed pathlib dependency
* Set up bump2version
test with emu ... still seems to work. |
@tlvu @Zeitsperre Maybe you like to check this PR? We can still improve on pywps-4.4 also after merge ... |
@cehbrecht I have opened a new PR: #575. Feel free to merge at your leisure! |
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.
Looks good to me. For the Mmmetype list, I can't help but notice that the GeoTIFF mimetype is a matter of intense debate (opengeospatial/geotiff#34). Does it make sense to include Format('image/tiff', extension='.tiff', encoding='base64')
as well? What are your thoughts?
Also, cosmetic opinion, but would you be open to isort
-ing the library imports to clean them up a bit?
@Zeitsperre @fmigneault Thanks for the review. Please give the pywps-4.4 branch a try ... when there are no complains I can make the 4.4.0 release. |
@cehbrecht sorry I took a day off yesterday, was not able to look at this sooner. So basically if we diff this branch with |
Here is how Looks like all the changes from 4.2.4 forward are missing on |
Here is the reverse diff (if Looks like mostly the jobqueue but there are other changes that I am not familiar with. |
I feel it would be a great idea to have first the resolution of python 2/3 with minor patches in 4.4. I have started pointing at I fear though that the alembic database migration and all other job queue elements would cause a lot of problems on my side, while being unnecessary in |
@fmigneault In the next attempt for the job queue implementation I would prefer to life without alembic database migration. The database is essentially used for the queue and this is just temporary storage. |
I could create a dev-branch from the current |
I am not suggesting merging The 2 compare links I generated is simply for us to audit the changes between |
I think we simply just need to return to the regular workflow. Correct me if I am wrong but we used to merge all branches back to So when we create new branches from If what I understood is correct, then after the merge of |
Right. The job-queue is not on |
When me make a new attempt on the job-queue I would do this on a dev branch. We can merge it to master when we are really sure we want to keep it 😄 The next things that could happen on master (after re-integration of pywps-4.4):
|
Correct. I did not literally meant any commits direct on Sorry if my message was not clear. Nothing should land on |
Overview
This branch backports the changes on master to pywps 4.4.
Related Issue / Discussion
#568
Additional Information
List of integrated PRs:
Skipped PRs:
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)