Make vdm 0.11 a PyPI package dependency

[amercader]

I just had to install CKAN in an offline environment. It would have helped if the CKAN dependencies were all non-editable ie. published as packages on PyPI (e.g. like this).

vdm is the only editable dependency left because vdm==0.11 is not published on PyPI (see okfn/vdm#5 ).

[tobes]

@kindly were you looking to remove vdm?

[stefanw]

I had another look into this and the difference between the released vdm-0.10 and non-released vdm-0.11 is only logging and error messages.

@kindly @rgrp Please publish vdm-0.11 to PyPI or fix the dependency in CKAN to vdm-0.10.

I'm doing deployment consulting for an "offline" environment where I need to bring packages with me and therefore need published packages instead of editable resources as dependencies.

Removing editable resources will also make installs faster as packages can be cached locally and can be put on their own pip-mirror etc.

[tobes]

@stefanw rgrp no longer does ckan development I realise that vdm may be owned by him

[stefanw]

@tobes I know, but @rgrp was involved in vdm and likely is the one person who can push a new release to PyPI.

[stefanw]

I'm disappointed to see that this is commit is not part of the 2.0 release. This will make deploying a stable 2.0 much more difficult.

[tobes]

@amercader where is this at? do we need a pull request? maybe we should backport to 2.0.1?

[amercader]

When this was proposed, 2.0 was in the pre-release freeze and changes in requirements are generally not accepted then. The issue was flagged as 2.1 and no objections were raised to it.
I understand that this is not a requirement change per se so I'm happy to backport it to 2.0.1.
@stefanw that will mean that the package install will then include this change.