nixpkgs-suyu/pkgs/development/python-modules/atomicwrites/default.nix

{ stdenv, buildPythonPackage, fetchPypi, pytest }:

buildPythonPackage rec {
  pname = "atomicwrites";
  version = "1.3.0";

  src = fetchPypi {
    inherit pname version;
    sha256 = "75a9445bac02d8d058d5e1fe689654ba5a6556a1dfd8ce6ec55a0ed79866cfa6";
  };

  # Tests depend on pytest but atomicwrites is a dependency of pytest
  doCheck = false;
  checkInputs = [ pytest ];

  meta = with stdenv.lib; {
    description = "Atomic file writes on POSIX";
    homepage = https://pypi.python.org/pypi/atomicwrites;
    maintainers = with maintainers; [ matthiasbeyer ];
  };
}
Split buildPythonPackage into setup hooks This commit splits the `buildPythonPackage` into multiple setup hooks. Generally, Python packages are built from source to wheels using `setuptools`. The wheels are then installed with `pip`. Tests were often called with `python setup.py test` but this is less common nowadays. Most projects now use a different entry point for running tests, typically `pytest` or `nosetests`. Since the wheel format was introduced more tools were built to generate these, e.g. `flit`. Since PEP 517 is provisionally accepted, defining a build-system independent format (`pyproject.toml`), `pip` can now use that format to execute the correct build-system. In the past I've added support for PEP 517 (`pyproject`) to the Python builder, resulting in a now rather large builder. Furthermore, it was not possible to reuse components elsewhere. Therefore, the builder is now split into multiple setup hooks. The `setuptoolsCheckHook` is included now by default but in time it should be removed from `buildPythonPackage` to make it easier to use another hook (curently one has to pass in `dontUseSetuptoolsCheck`). 2019-07-17 20:36:47 +02:00			`{ stdenv, buildPythonPackage, fetchPypi, pytest }:`
pythonPackages.atomicwrites: Move to own file 2018-03-31 11:31:12 +02:00
			`buildPythonPackage rec {`
			`pname = "atomicwrites";`
python: atomicwrites: 1.2.1 -> 1.3.0 2019-02-14 08:37:10 +01:00			`version = "1.3.0";`
pythonPackages.atomicwrites: Move to own file 2018-03-31 11:31:12 +02:00
			`src = fetchPypi {`
			`inherit pname version;`
python: atomicwrites: 1.2.1 -> 1.3.0 2019-02-14 08:37:10 +01:00			`sha256 = "75a9445bac02d8d058d5e1fe689654ba5a6556a1dfd8ce6ec55a0ed79866cfa6";`
pythonPackages.atomicwrites: Move to own file 2018-03-31 11:31:12 +02:00			`};`

Split buildPythonPackage into setup hooks This commit splits the `buildPythonPackage` into multiple setup hooks. Generally, Python packages are built from source to wheels using `setuptools`. The wheels are then installed with `pip`. Tests were often called with `python setup.py test` but this is less common nowadays. Most projects now use a different entry point for running tests, typically `pytest` or `nosetests`. Since the wheel format was introduced more tools were built to generate these, e.g. `flit`. Since PEP 517 is provisionally accepted, defining a build-system independent format (`pyproject.toml`), `pip` can now use that format to execute the correct build-system. In the past I've added support for PEP 517 (`pyproject`) to the Python builder, resulting in a now rather large builder. Furthermore, it was not possible to reuse components elsewhere. Therefore, the builder is now split into multiple setup hooks. The `setuptoolsCheckHook` is included now by default but in time it should be removed from `buildPythonPackage` to make it easier to use another hook (curently one has to pass in `dontUseSetuptoolsCheck`). 2019-07-17 20:36:47 +02:00			`# Tests depend on pytest but atomicwrites is a dependency of pytest`
			`doCheck = false;`
			`checkInputs = [ pytest ];`

pythonPackages.atomicwrites: Move to own file 2018-03-31 11:31:12 +02:00			`meta = with stdenv.lib; {`
			`description = "Atomic file writes on POSIX";`
			`homepage = https://pypi.python.org/pypi/atomicwrites;`
			`maintainers = with maintainers; [ matthiasbeyer ];`
			`};`
			`}`