How to Install and Uninstall python311-httpbin Package on openSUSE Leap
Last updated: December 25,2024
1. Install "python311-httpbin" package
This is a short guide on how to install python311-httpbin on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python311-httpbin
Copied
2. Uninstall "python311-httpbin" package
This is a short guide on how to uninstall python311-httpbin on openSUSE Leap:
$
sudo zypper remove
python311-httpbin
Copied
3. Information about the python311-httpbin package on openSUSE Leap
Information for package python311-httpbin:
------------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : python311-httpbin
Version : 0.7.0+git20181107.f8ec666-150400.11.3.6
Arch : noarch
Vendor : SUSE LLC
Installed Size : 277.8 KiB
Installed : No
Status : not installed
Source package : python-httpbin-0.7.0+git20181107.f8ec666-150400.11.3.6.src
Upstream URL : https://github.com/Runscope/httpbin
Summary : HTTP Request and Response Service
Description :
httpbin(1): HTTP Request & Response Service
Testing an HTTP Library can become difficult sometimes.
RequestBin is fantastic for testing POST requests, but doesn't let
you control the response. This exists to cover
all kinds of HTTP scenarios. Additional endpoints are being considered.
All endpoint responses are JSON-encoded.
------------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : python311-httpbin
Version : 0.7.0+git20181107.f8ec666-150400.11.3.6
Arch : noarch
Vendor : SUSE LLC
Installed Size : 277.8 KiB
Installed : No
Status : not installed
Source package : python-httpbin-0.7.0+git20181107.f8ec666-150400.11.3.6.src
Upstream URL : https://github.com/Runscope/httpbin
Summary : HTTP Request and Response Service
Description :
httpbin(1): HTTP Request & Response Service
Testing an HTTP Library can become difficult sometimes.
RequestBin is fantastic for testing POST requests, but doesn't let
you control the response. This exists to cover
all kinds of HTTP scenarios. Additional endpoints are being considered.
All endpoint responses are JSON-encoded.