The test cases are disabled because
Dependency list is huge.
https://github.com/mapproxy/mapproxy/blob/master/requirements-tests.txt
There are security issues with package Riak
#33876
#56480

I've done some checks in the source code regarding the usage of libraries. I found that:

• There's a MAPPROXY_LIB_PATH that can be used to add paths to C .so objects or dlls so that the system can load C libraries to bind to.
• The 2 C libraries that it makes use of are: libproj and libgdal. These are not necessary if the 2 python fallbacks are available: pyproj and gdal.

So in the example derivation I pasted above, it just has pyproj and gdal.

When I tried building locally with nix-build:

{
  pkgs ? (import (fetchTarball https://github.com/NixOS/nixpkgs-channels/archive/83e01aa5e48a9107f3b988c9d4c1c21d610626fb.tar.gz) {}),
  pythonPath ? "python37"
}:
  with pkgs;
  let
    python = lib.getAttrFromPath (lib.splitString "." pythonPath) pkgs;
  in
    python.pkgs.buildPythonPackage rec {
      pname = "MapProxy";
      version = "1.12.0";

      src = python.pkgs.fetchPypi {
        inherit pname version;
        sha256 = "622e3a7796ef861ba21e42231b49c18d00d75f03eaf3f01a2b7687be7568e2ec";
      };

      propagatedBuildInputs = with python.pkgs; [
        pillow
        pyyaml
        pyproj
        shapely
        gdal
        lxml
      ];

      doCheck = false;

      meta = with lib; {
        description = "MapProxy is an open source proxy for geospatial data";
        homepage = https://mapproxy.org/;
        license = licenses.asl20;
        maintainers = with maintainers; [ rakesh4g ];
      };
    }

Every works fine. But I use the callPackage pattern required by python-modules in Nixpkgs, I end up with this error:

nix-build ./default.nix --attr pkgs.python3Packages.mapproxy

»» ~/Projects/nixpkgs
 ♖ ./result/bin/mapproxy-util --version
Traceback (most recent call last):
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/bin/.mapproxy-util-wrapped", line 7, in <module>
    from mapproxy.script.util import main
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/lib/python3.7/site-packages/mapproxy/script/util.py", line 28, in <module>
    from mapproxy.script.conf.app import config_command
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/lib/python3.7/site-packages/mapproxy/script/conf/app.py", line 32, in <module>
    from .sources import sources
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/lib/python3.7/site-packages/mapproxy/script/conf/sources.py", line 17, in <module>
    from mapproxy.srs import SRS
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/lib/python3.7/site-packages/mapproxy/srs.py", line 26, in <module>
    from mapproxy.proj import Proj, transform, set_datapath
  File "/nix/store/3vbi2pfcf9bh0x535k78ln9p371xd7h5-python3.7-MapProxy-1.12.0/lib/python3.7/site-packages/mapproxy/proj.py", line 262, in <module>
    raise ImportError('could not find libproj or pyproj')
ImportError: could not find libproj or pyproj

Why would using the call package pattern result in such a difference? Given that my out-of-tree default.nix uses an older nixpkgs hash, it just means setuptools is part of the package environment, whereas the current nixpkgs master doesn't have that.

Furthermore this is not the only problem. Even though my bin/mapproxy-util works, it fails to work as server due to probably the application considering that bin/mapproxy-util is a python script and trying to run it with python, but it fails with a syntax error because the bin/mapproxy-util is a wrapped shell script due to Nix.

»» ~/Projects/mapproxy/mymapproxy
 ♖ ../result/bin/mapproxy-util serve-develop mapproxy.yaml
[2019-10-02 13:22:18,621] mapproxy.config - INFO - reading: /home/cmcdragonkai/Projects/mapproxy/mymapproxy/mapproxy.yaml
[info]  * Running on http://127.0.0.1:8080/ (Press CTRL+C to quit)
[info]  * Restarting with reloader
  File "/nix/store/bfvw32p8c61jajjm7a8z98xbk1n6qiwz-python3.7-MapProxy-1.12.0/bin/mapproxy-util", line 2
    export PATH='/nix/store/kimimvhimclyfzlncpg36zjni3wn70nq-python3-3.7.3/bin:/nix/store/bfvw32p8c61jajjm7a8z98xbk1n6qiwz-python3.7-MapProxy-1.12.0/bin:/nix/store/rpayih9fb4ms2wjvmyn6kp7kmsizim49-python3.7-setuptools-40.8.0/bin:/nix/store/kp0g7z5h4kr6gx71jf9q0a9322p4jr5p-python3.7-numpy-1.16.2/bin:/nix/store/7vgnq00rxw9xh03920apdyj4ibgsmrix-gdal-2.4.0/bin'${PATH:+':'}$PATH
              ^
SyntaxError: invalid syntax

I've reported this problem on mapproxy: mapproxy/mapproxy#424

@Rakesh4G Also this is more of an application, not a package. Maybe we should be changing it to buildPythonApplication? Can you try changing this PR structure to instead mimic dvc's style: #54530

Notice where the default.nix is placed. It's not in python-modules.

Is there any progress on it?

Is there any progress on it?

I am still waiting on some guidance to alternate options due to
#68628 (comment)

This can not be merged as is.
With Latest pyproj mapproxy breaks.
details here:
mapproxy/mapproxy#417

So we might need to add pyproj version - 1.9.6, With this version Mapproxy works.
@CMCDragonkai @FRidh

If pyproj 2 is way different from pyproj1, we might need to keep a pyproj1 around in a separate derivation.

If pyproj 2 is way different from pyproj1, we might need to keep a pyproj1 around in a separate derivation.

@CMCDragonkai , OK. I will create a new PR to add support for pyproj1 as separate derivation.

Added PR for pyproj1:
#78092

should be just 1 commit, please squash.

git reset HEAD^^
git add pkgs/
git commit --amend --no-edit
git push .. .. --force

should be just 1 commit, please squash.

git reset HEAD^^
git add pkgs/
git commit --amend --no-edit
git push .. .. --force

ok.

@GrahamcOfBorg build mapproxy

Hi @jonringer , sorry i made one mistake. it is supposed to be a buildPythonApplication not buildPythonPackage. I am just updating this in a minute.

@GrahamcOfBorg build mapproxy