Files
openRuyi/SPECS/python-ptyprocess/python-ptyprocess.spec

50 lines
1.6 KiB
RPMSpec
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# SPDX-FileCopyrightText: (C) 2026 Institute of Software, Chinese Academy of Sciences (ISCAS)
# SPDX-FileCopyrightText: (C) 2026 openRuyi Project Contributors
# SPDX-FileContributor: purofle <yuguo.or@isrc.iscas.ac.cn>
#
# SPDX-License-Identifier: MulanPSL-2.0
%global srcname ptyprocess
Name: python-%{srcname}
Version: 0.7.0
Release: %autorelease
Summary: Run a subprocess in a pseudo terminal
License: ISC
URL: https://github.com/pexpect/ptyprocess
#!RemoteAsset: sha256:5c5d0a3b48ceee0b48485e0c26037c0acd7d29765ca3fbb5cb3831d347423220
Source0: https://files.pythonhosted.org/packages/source/p/%{srcname}/%{srcname}-%{version}.tar.gz
BuildArch: noarch
BuildSystem: pyproject
BuildOption(install): -l %{srcname}
BuildRequires: pyproject-rpm-macros
BuildRequires: pkgconfig(python3)
BuildRequires: python3dist(setuptools)
BuildRequires: python3dist(pip)
BuildRequires: python3dist(wheel)
BuildRequires: python3dist(flit-core)
Provides: python3-%{srcname}
%python_provide python3-%{srcname}
%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
doesnt read from stdin, output that changes when its 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.
%generate_buildrequires
%pyproject_buildrequires
%files -f %{pyproject_files}
%doc README.rst
%license LICENSE
%changelog
%{?autochangelog}