You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce, simply download a wheel, e.g., z3_solver-4.14.1.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, from https://pypi.org/project/z3-solver/#files and unzip it. There's no license file.
The license file is however present in the corresponding source distribution, in the core folder.
The license says "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." so it really should be included in the wheels.
The text was updated successfully, but these errors were encountered:
If you have bandwidth to add it to the process that uses setup.py to build the wheels it is good.
There are already some references to LICENSE.txt in setup.py but these don't result in including them.
Update setup.py so that we copy LICENSE.TXT to src/api/python before
creating the sdist. Any wheels built from this sdist will now
contain the LICENSE.txt file.
FixesZ3Prover#7604
Update setup.py so that we copy LICENSE.TXT to src/api/python before
creating the sdist. Any wheels built from this sdist will now
contain the LICENSE.txt file.
Fixes#7604
Update setup.py so that we copy LICENSE.TXT to src/api/python before
creating the sdist. Any wheels built from this sdist will now
contain the LICENSE.txt file.
FixesZ3Prover#7604
To reproduce, simply download a wheel, e.g., z3_solver-4.14.1.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, from https://pypi.org/project/z3-solver/#files and unzip it. There's no license file.
The license file is however present in the corresponding source distribution, in the core folder.
The license says "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." so it really should be included in the wheels.
The text was updated successfully, but these errors were encountered: