# # spec file for package python-ptyprocess # # Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # Name: python-ptyprocess Version: 0.5.1 Release: 0 Summary: Run a subprocess in a pseudo terminal License: ISC Group: Development/Languages/Python Url: https://github.com/pexpect/ptyprocess Source: https://pypi.io/packages/source/p/ptyprocess/ptyprocess-%{version}.tar.gz BuildRequires: python-devel >= 2.7 BuildRequires: python-nose BuildRequires: python-setuptools BuildRoot: %{_tmppath}/%{name}-%{version}-build %if 0%{?suse_version} && 0%{?suse_version} <= 1110 %{!?python_sitelib: %global python_sitelib %(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")} %else BuildArch: noarch %endif %description Launch a subprocess in a pseudo terminal (pty), and interact with both the process and its pty. Sometimes, piping stdin and stdout is not enough. There might be a password prompt that doesn't read from stdin, output that changes when it's going to a pipe rather than a terminal, or curses-style interfaces that rely on a terminal. If you need to automate these things, running the process in a pseudo terminal (pty) is the answer. %prep %setup -q -n ptyprocess-%{version} %build python setup.py build %install python setup.py install --prefix=%{_prefix} --root=%{buildroot} %check nosetests %files %defattr(-,root,root,-) %doc README.rst %{python_sitelib}/* %changelog