Arch Linux User Repository

I'm not a fan of bumping in those cases. Without a bump, the program fails for users, but they know afterwards they need to rebuild it. If pkgrel is bumped there still could be the issue, that someone still runs python3.8 and after an upgrade still has a broken package.
Either way has its quirks.

Can you bump the package number so it prompts helpers to rebuild this package? It needs to be rebuilt for python 3.9 to work again.

Thanks for the research bmwinger. If it is solved by switching the location of the source, then I will do this change.

The contents of /usr/lib/python3.6/site-packages/patool-1.12-py3.6.egg-info/ seem to be lacking read permissions, 640 rather than 644. This causes all python imports to fail

It looks like the issue here is that the archive on pypi already contains a patool.egg-info directory with 640 permissions. Removing this before building the package, or using the archive from github (which doesn't come with patool.egg-info already built) will create the patool.egg-info directory with the correct permissions.

Error importing module named 'setuptools'.

Traceback (most recent call last):
  File "setup.py", line 26, in <module>
    from setuptools import setup
ImportError: No module named setuptools
==> ERROR: A failure occurred in package_patool-py2().
    Aborting...
Error making: patool

Since ever, or since the change where I added --optimize=1?
If the first, then it should probably be brought to upstream

The contents of /usr/lib/python3.6/site-packages/patool-1.12-py3.6.egg-info/ seem to be lacking read permissions, 640 rather than 644.

This causes all python imports to fail

@jschmoe: It seems yaourt cannot handle packages that are from the same PKGBuild and conflicting each other. This is a fault in yaourt. The issue should be avoided if you remove the conflicts line (aka both packages should be build).
The naming and setting of variables itself is correct (see Split-PKGBuilds. The pkgbase var can just hold the main and only name. In pkgname you can declare all the names of all the packages you want to create with the PKGBuild)
The conclicts line is somewhat necessary because the binary is installed with both python versions under patool and I didn't want to rename one of the binaries (Could be misleading if patool2 or whatever). And it doesn't make sense to have both python versions installed.

i still get the following error until i change pkgname=('patool' 'patool-py2')
into pkgname=('patool') in the PKGBUILD. maybe you can't have two names there?!
haven't tried to install patool-py2 but i think the installation works with pkgname=('patool-py2')

resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: patool-py2 and patool are in conflict
==> WARNING: Your packages are saved in /tmp/yaourt-....

@jschmoe: And how to diff between the python2 and python3 packages? They're separate packages, not one package that installs python2 and python3 version

@dront78: DL is working for me (but there is a redirect now). But will change it to the pypi dl-link as the homepage now points to it