diff --git a/ptyprocess-0.6.0.tar.gz b/ptyprocess-0.6.0.tar.gz new file mode 100644 index 0000000..f0d3295 Binary files /dev/null and b/ptyprocess-0.6.0.tar.gz differ diff --git a/python-ptyprocess.spec b/python-ptyprocess.spec new file mode 100644 index 0000000..9d9eb7f --- /dev/null +++ b/python-ptyprocess.spec @@ -0,0 +1,82 @@ +%global with_tests 0%{?_with_tests:1} +Name: python-ptyprocess +Version: 0.6.0 +Release: 3 +Summary: Run a subprocess in a pseudo terminal + +License: ISC +URL: https://github.com/pexpect/ptyprocess +Source0: https://files.pythonhosted.org/packages/source/p/ptyprocess/ptyprocess-%{version}.tar.gz + +BuildArch: noarch +BuildRequires: python2-devel pytest python%{python3_pkgversion}-devel python%{python3_pkgversion}-pytest + +%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. + +%package -n python2-ptyprocess +Summary: Run a subprocess in a pseudo terminal +%python_provide python2-ptyprocess +%description -n python2-ptyprocess +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. + +%package -n python%{python3_pkgversion}-ptyprocess +Summary: Run a subprocess in a pseudo terminal +%python_provide python%{python3_pkgversion}-ptyprocess +%description -n python%{python3_pkgversion}-ptyprocess +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 +%autosetup -n ptyprocess-%{version} -p1 + +%build +%py2_build +LC_ALL=en_US.UTF-8 \ + %py3_build + +%install +LC_ALL=en_US.UTF-8 \ + %py3_install +%py2_install + +%check +%if %{with_tests} +%{_bindir}/py.test-3.* -v +%{_bindir}/py.test-2.* -v +%endif + +%files -n python2-ptyprocess +%doc LICENSE README.rst +%{python2_sitelib}/ptyprocess/ +%{python2_sitelib}/ptyprocess-%{version}-py?.?.egg-info + +%files -n python%{python3_pkgversion}-ptyprocess +%doc LICENSE README.rst +%{python3_sitelib}/ptyprocess/ +%{python3_sitelib}/ptyprocess-%{version}-py?.?.egg-info + +%changelog +* Tue Feb 18 2020 chenli - 0.6.0-3 +- init package +