pythonPackages.pexpect: 4.2.1 -> 4.3.0

+45 -37
+44
pkgs/development/python-modules/pexpect/default.nix
··· 1 + { lib 2 + , buildPythonPackage 3 + , fetchPypi 4 + , ptyprocess 5 + }: 6 + 7 + buildPythonPackage rec { 8 + pname = "pexpect"; 9 + version = "4.3.0"; 10 + name = "${pname}-${version}"; 11 + 12 + src = fetchPypi { 13 + inherit pname version; 14 + sha256 = "1nfjmz81gsixv22dywidakm7pff3ly1i4yly950bfp8gz1r0iaq0"; 15 + }; 16 + 17 + # Wants to run pythonin a subprocess 18 + doCheck = false; 19 + 20 + propagatedBuildInputs = [ ptyprocess ]; 21 + 22 + meta = with lib; { 23 + homepage = http://www.noah.org/wiki/Pexpect; 24 + description = "Automate interactive console applications such as ssh, ftp, etc"; 25 + license = licenses.mit; 26 + maintainers = with maintainers; [ zimbatm ]; 27 + 28 + longDescription = '' 29 + Pexpect is similar to the Don Libes "Expect" system, but Pexpect 30 + as a different interface that is easier to understand. Pexpect 31 + is basically a pattern matching system. It runs programs and 32 + watches output. When output matches a given pattern Pexpect can 33 + respond as if a human were typing responses. Pexpect can be used 34 + for automation, testing, and screen scraping. Pexpect can be 35 + used for automating interactive console applications such as 36 + ssh, ftp, passwd, telnet, etc. It can also be used to control 37 + web applications via "lynx", "w3m", or some other text-based web 38 + browser. Pexpect is pure Python. Unlike other Expect-like 39 + modules for Python Pexpect does not require TCL or Expect nor 40 + does it require C extensions to be compiled. It should work on 41 + any platform that supports the standard Python pty module. 42 + ''; 43 + }; 44 + }
+1 -37
pkgs/top-level/python-packages.nix
··· 14386 14386 }; 14387 14387 }; 14388 14388 14389 - 14390 - pexpect = buildPythonPackage rec { 14391 - version = "4.2.1"; 14392 - name = "pexpect-${version}"; 14393 - 14394 - src = pkgs.fetchurl { 14395 - url = "mirror://pypi/p/pexpect/${name}.tar.gz"; 14396 - sha256 = "3d132465a75b57aa818341c6521392a06cc660feb3988d7f1074f39bd23c9a92"; 14397 - }; 14398 - 14399 - # Wants to run pythonin a subprocess 14400 - doCheck = false; 14401 - 14402 - propagatedBuildInputs = with self; [ ptyprocess ]; 14403 - 14404 - meta = { 14405 - homepage = http://www.noah.org/wiki/Pexpect; 14406 - description = "Automate interactive console applications such as ssh, ftp, etc"; 14407 - license = licenses.mit; 14408 - 14409 - longDescription = '' 14410 - Pexpect is similar to the Don Libes "Expect" system, but Pexpect 14411 - as a different interface that is easier to understand. Pexpect 14412 - is basically a pattern matching system. It runs programs and 14413 - watches output. When output matches a given pattern Pexpect can 14414 - respond as if a human were typing responses. Pexpect can be used 14415 - for automation, testing, and screen scraping. Pexpect can be 14416 - used for automating interactive console applications such as 14417 - ssh, ftp, passwd, telnet, etc. It can also be used to control 14418 - web applications via "lynx", "w3m", or some other text-based web 14419 - browser. Pexpect is pure Python. Unlike other Expect-like 14420 - modules for Python Pexpect does not require TCL or Expect nor 14421 - does it require C extensions to be compiled. It should work on 14422 - any platform that supports the standard Python pty module. 14423 - ''; 14424 - }; 14425 - }; 14389 + pexpect = callPackage ../development/python-modules/pexpect { }; 14426 14390 14427 14391 pdfkit = buildPythonPackage rec { 14428 14392 name = "pdfkit-${version}";