GPL-3 places different obligations for conveying "source code" and "object code distribution". See GPL 3.0 / 4. Conveying Verbatim Copies and GPL 3.0 / 6. Conveying Non-Source Forms. Among other things:
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways [GPL-3.0-S6]
Would python wheels (see examples from psutil here here) be considered "object code" or "source code"?
Wheels in many cases are just ZIP archives with the source code and some metadata - so I think there could be a compelling case to be made than if a tarball of source is source form then so is a python wheel.
Here is a listing of the content of one of the psutils wheels:
$ bsdtar -tf <(curl --silent https://files.pythonhosted.org/packages/13/a7/626f257d22168c954fd3ad69760c02bdec27c0648a62f6ea5060c4d40672/psutil-5.6.7-cp27-none-win32.whl)
psutil/__init__.py
psutil/_common.py
psutil/_compat.py
psutil/_psaix.py
psutil/_psbsd.py
psutil/_pslinux.py
psutil/_psosx.py
psutil/_psposix.py
psutil/_pssunos.py
psutil/_psutil_windows.pyd
psutil/_pswindows.py
psutil/tests/__init__.py
psutil/tests/__main__.py
psutil/tests/runner.py
psutil/tests/test_aix.py
psutil/tests/test_bsd.py
psutil/tests/test_connections.py
psutil/tests/test_contracts.py
psutil/tests/test_linux.py
psutil/tests/test_memory_leaks.py
psutil/tests/test_misc.py
psutil/tests/test_osx.py
psutil/tests/test_posix.py
psutil/tests/test_process.py
psutil/tests/test_sunos.py
psutil/tests/test_system.py
psutil/tests/test_unicode.py
psutil/tests/test_windows.py
psutil-5.6.7.dist-info/LICENSE
psutil-5.6.7.dist-info/METADATA
psutil-5.6.7.dist-info/WHEEL
psutil-5.6.7.dist-info/top_level.txt
psutil-5.6.7.dist-info/RECORD
Maybe the answer is that it depends on the content of the wheel?