Dmitri Bogomolov

Currently we don't build on Focal and recommend to use appimage on distros newer than Bionic.

Wrong placement. There shouldn't be a `mock` package, because the end user doesn't need it. Please move into tests.

> the first PR will add allow travis to run python3 while successfully doing nothing. The pybitmessage binary will check if it's running python 3 and if yes, exit with...

> Not sure what to do if requirements.txt diverge between python 2 and python 3. Unlikely

> @g1itch I don't have python2! It is not supported in any new OS. Not even in Debian 11! > > I need a Debian 10 virtual machine with Gnome...

> Then there are other minor issues, like travis2bash not understanding the full travis syntax, the non-developers not having proper feedback. It seems that `python: - "3.6"` is OK for...

> I'll add python 3.6 into the VMs and then rerun your tests, but it may take a couple of days. There is no rush. If you take a close...

> just as to make sure that PyBitmessage works above Python 3.5 at least. PyBitmessage currently does not support python3.

It seems I read here something you didn't write and maybe didn't even mean. Do you agree that if somebody wants to participate in the porting process, he should: 1....

Meanwhile the [official doc](https://docs.python.org/3/howto/pyporting.html) explicitly mentions test coverage and the bad practice of using `sys.version_info`: https://docs.python.org/3/howto/pyporting.html#use-feature-detection-instead-of-version-detection As for requirements, you can separate them by version using [environment markers](https://www.python.org/dev/peps/pep-0508/#environment-markers) e.g. ```diff...