I'd prefer to use Python 3 on EPEL 7.

Switched to Python 3.

Maybe a newer release of the package can be pushed as python3 packages are newer, but I'll need more time to test and prefer to get this one for now.

+ /usr/bin/python3 setup.py build
Traceback (most recent call last):
  File "setup.py", line 111, in <module>
    'Topic :: Utilities'
  File "/usr/lib/python3.6/site-packages/setuptools/__init__.py", line 128, in setup
    _install_setup_requires(attrs)
  File "/usr/lib/python3.6/site-packages/setuptools/__init__.py", line 121, in _install_setup_requires
    dist.parse_config_files(ignore_option_errors=True)
  File "/usr/lib/python3.6/site-packages/setuptools/dist.py", line 492, in parse_config_files
    _Distribution.parse_config_files(self, filenames=filenames)
  File "/usr/lib64/python3.6/distutils/dist.py", line 395, in parse_config_files
    parser.read(filename)
  File "/usr/lib64/python3.6/configparser.py", line 697, in read
    self._read(fp, filename)
  File "/usr/lib64/python3.6/configparser.py", line 1015, in _read
    for lineno, line in enumerate(fp, start=1):
  File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 379: ordinal not in range(128)

Try setting LANG=en_US.utf-8

This is a diff from your epel8 specfile that builds on epel8:

diff --git a/httpie.spec b/httpie.spec
index bd0467d..4aaa32f 100644
--- a/httpie.spec
+++ b/httpie.spec
@@ -30,14 +30,19 @@ Patch5:         https://github.com/httpie/httpie/pull/1075.patch

 BuildArch:      noarch

-BuildRequires:  python3-devel
-BuildRequires:  python3-setuptools
-BuildRequires:  python3-pygments
-BuildRequires:  python3-requests
-BuildRequires:  python3-requests-toolbelt
+BuildRequires:  python36-devel
+BuildRequires:  python36-setuptools
+BuildRequires:  python36-pygments
+BuildRequires:  python36-requests
+BuildRequires:  python36-requests-toolbelt
 BuildRequires:  sed
 BuildRequires:  help2man

+Requires:       python36-setuptools
+Requires:       python36-pygments
+Requires:       python36-requests
+Requires:       python36-requests-toolbelt
+
 %description
 HTTPie is a CLI HTTP utility built out of frustration with existing tools. The
 goal is to make CLI interaction with HTTP-based services as human-friendly as
@@ -55,15 +60,19 @@ sed -i '/#!\/usr\/bin\/env/d' httpie/__main__.py
 # RHEL8 ships version 2.2, which works fine here.
 sed -i 's/Pygments>=2.5.2/Pygments>=2.2.0/' setup.py

+sed -i 's/requests-toolbelt>=0.9.1/requests-toolbelt>=0.8/' setup.py
+
 # RHEL8 ships version 2.22.0 which works fine here.
-sed -i 's/requests\[socks\]>=2.22.0/requests>=2.20.0/' setup.py
+sed -i 's/requests\[socks\]>=2.22.0/requests>=2.14.2/' setup.py


 %build
+export LANG=en_US.utf-8
 %py3_build


 %install
+export LANG=en_US.utf-8
 %py3_install

 # Bash completion

Sorry Miro, where did it fail that required the LANG export?

i did a scratch-build an is working fine https://koji.fedoraproject.org/koji/taskinfo?taskID=73587049

Here in the Fedora CI - scratch build job.

The sha512sum of the source tarball here is 80e540dcb92a55fb8b3c5dd56f380cb1795e4296827591853070a5b775c1f87cd881758d9dd0bdfeff383d06ce8ffafe68ec0269e3d269473e528952a769ecb7

The sha512sum of the source tarball from your scratchbuild is b51779e0ec8f24108ee3f4bf690dc9dfddafff42509d1aa3d13ac12d65a93e02aad9644dc10134ebdbebf949b250cb288650a4dad3d382143e9ad3b9b0ac8c16

Your scratchbould only works because it uses a tarball that is missing some of the non-ASCII characters.

The sha512sum of the source tarball here is 80e540dcb92a55fb8b3c5dd56f380cb1795e4296827591853070a5b775c1f87cd881758d9dd0bdfeff383d06ce8ffafe68ec0269e3d269473e528952a769ecb7

The sha512sum of the source tarball from your scratchbuild is b51779e0ec8f24108ee3f4bf690dc9dfddafff42509d1aa3d13ac12d65a93e02aad9644dc10134ebdbebf949b250cb288650a4dad3d382143e9ad3b9b0ac8c16

It may be that I had the pypy version downloaded. It fails with the one from GitHub, so added the export LANG commands and is working now.

The package should be httpie and not python3-httpie and it needs to obsolete python2-httpie, otherwise the upgrade won't work.

The package should be httpie and not python3-httpie and it needs to obsolete python2-httpie, otherwise the upgrade won't work.

Added obsolete on python2-httpie, but not sure about the naming. I removed the python3 subpackage, so it's not python3-httpie anymore. You refer this way?

No need to obsolete httpie, this is httpie.

If you remove this mv...

...you don't need this ln -s.

I removed the python3 subpackage, so it's not python3-httpie anymore. You refer this way?

Yes, thanks!

With the following local changes:

diff --git a/httpie.spec b/httpie.spec
index 0b892b8..f543f97 100644
--- a/httpie.spec
+++ b/httpie.spec
@@ -13,6 +13,9 @@ Obsoletes:      python2-httpie < 0.9.5
 Requires:       python3
 Requires:       python36-pygments
 Requires:       python36-requests
+BuildRequires:       python36-pygments
+BuildRequires:       python36-requests
+BuildRequires:       python36-mock

 BuildRequires:  python3-devel
 BuildRequires:  python3-setuptools
@@ -45,8 +48,13 @@ export LANG=en_US.utf-8
 %{__python3} setup.py install --root %{buildroot}

 # pytest-httpbin is not available in EPEL7, can't run checks
-#%%check
-#%%pytest -v
+%check
+rm build -rf
+export LANG=en_US.utf-8
+export PATH="%{buildroot}%{_bindir}:$PATH"
+export PYTHONPATH="${PYTHONPATH:-%{buildroot}%{python3_sitearch}:%{buildroot}%{python3_sitelib}}"
+export PYTHONDONTWRITEBYTECODE=1
+pytest -vvv

 %files
 %doc README.rst

And installing pytest + pytest-httpbin via pip, I get:

$ fedpkg --release epel7 mockbuild -N --enable-network
...
=========================== short test summary info ============================
FAILED tests/test_ssl.py::test_ssl_version[ssl3] - requests.exceptions.Connec...
FAILED tests/test_ssl.py::TestClientCert::test_cert_file_invalid - requests.e...
FAILED tests/test_ssl.py::TestClientCert::test_cert_ok_but_missing_key - requ...
FAILED tests/test_ssl.py::TestServerCert::test_self_signed_server_cert_by_default_raises_ssl_error
FAILED tests/test_ssl.py::TestServerCert::test_verify_custom_ca_bundle_invalid_bundle
============ 5 failed, 226 passed, 9 skipped, 3 warnings in 15.39s =============

Most of this is caused by:

----------------------------- Captured stdout call -----------------------------
pytest-httpbin server hit an exception serving request: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:877)
attempting to ignore so the rest of the tests can run
----------------------------- Captured stderr call -----------------------------

http: error: ConnectionError: HTTPSConnectionPool(host='127.0.0.1', port=44211): Max retries exceeded with url: /get (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:877)'),)) while doing GET request to URL: https://127.0.0.1:44211/get

Not sure how bad this is.

The test_ssl_version[ssl3] fail is because httpbin doesn't support ssl3.

For the TestClientCert and TestServerCert I tested different ssl setups from badssl.com with 0.9.4 and 1.0.3 and I was not able to find anything broken in the new release. I would say they cover some corner cases that I'm sure 0.9.4 won't catch them either.