Hello, We have some python packages that uses the pypi .whl upstream distribution as "source" in the spec file and I'm trying to remove this from every package so we really build the package from source. It's true that for Python, a .whl and source package could be "the same" because of interpreted code, but it's also true that building from source is always better and safer because there's a third party building the software in a different environment. # Why we've some packages that uses .whl directly instead of building the package in OBS? Because there are some really complex packages that bundles "compiled" javascript, that's hard to replicate in a non connected environment like it's OBS. This pattern is common in jupyter related modules [1], that usually bundles a lot of javascript so we've some packages that just uses the .whl as source with an empty %build. # How to fix this? We've several options here to try to solve this issue, if you know about anything else, please, comment here so we can find the best solution. 1. Use the obs-service-node_modules [2] to build the javascript, like it's done in python-ipympl [3] 2. Bundle javascript manually and add a new source with node_modules.tar.xz, like it's done in python-jupyter-ydoc [4]. 3. Ask upstream to build the javascript or bundle the javascript in source releases so it's not needed to be added downstream (but maybe this is similar to use the .whl) As far as I know, these are the modules that still uses the .whl as source: * python-pythreejs * python-nbclassic * python-ipyevents * python-ipydatawidgets The task on the trello board [5]. Regards [1] https://build.opensuse.org/project/show/devel:languages:python:jupyter [2] https://github.com/openSUSE/obs-service-node_modules [3] https://build.opensuse.org/package/show/devel:languages:python:jupyter/pytho... [4] https://build.opensuse.org/package/show/devel:languages:python:jupyter/pytho... [5] https://trello.com/c/WVJLgkZ7/167-remove-usage-of-whl-file-as-source-of-pyth...