Skip to content
Advertisement

Tag: python-wheel

how to download and install wxPython wheel from github for Python 3.10 to overcome disutils and setuptools problem

Python 3.10 has a problem with disutils and setuptools>=58 in that wxPython will not run in conjunction with packages Gooey/DEAP/NEMO. I have been told there is a wxPython wheel which gets round those problems https://github.com/oleksis/youtube-dl-gui/releases/tag/v1.8.2 but i cannot get the command syntax to work for some relationship between: “git+”, #egg”, “wxPython” I tried pip install -e git+https://github.com/oleksis/youtube-dl-gui/releases/tag/v1.8.2/wxPython-4.1.2a1-cp310-cp310-win_amd64.whl#egg=wxPython and got pip

tkinter inter-windows drag and drop support

I’m trying to help the owner of tkdnd generate a wheel and distribute it to Pypi so users could simply install the tkdnd extension with a simple pip install TkinterDnD2. I’m after this ‘challange’ for the last two days but could not solve it by myself so far, but I’m sure someone with a deep understanding python packaging and installing

Wheel Incompatibility between Python Minor Versions

I’m releasing a package on PyPi which will support Python 3.6+, and would like to build as few wheels as possible. I’ve read up on Python’s packaging system for wheels and looked at the NumPy project for an example. Reading PEP 513 and PEP 571 was also insightful. Here’s the question: why are wheels forwards-incompatible with Python minor version changes?

Create wheel without building dependencies

I have a sample project: setup.py is just Then when I call pip wheel ., it automatically makes a wheel for numpy. Can I make it not do that? It’s my understanding that when you install a wheel, it will automatically go download and install any missing dependencies. Is the numpy wheel needed for making my test wheel? Answer That’s

How do I list the files inside a python wheel?

I’m poking around the various options to setup.py for including non-python files, and they’re somewhat less than intuitive. I’d like to be able to check the package generated by bdist_wheel to see what’s actually in it–not so much to make sure that it will work (that’s what tests are for) but to see the effects of the options I’ve set.

Advertisement