There was never a Django 1.0.7. The 1.0 series only went up to 1.0.4. You can see all the releases in the tags section of the Django code repository. However to answer your question, don’t use easy_install, use pip. (If it’s not already installed, do easy_install pip, then never touch easy_install again). Now you can … Read more
I was trying to get this to work for installing with pip, but the above was not working for me. From [1] I understood the PEP508 standard should be used, from [2] I retrieved an example which actually does work (at least for my case). Please note; this is with pip 20.0.2 on Python 3.7.4 … Read more
This is an excellent question. It took me forever to figure out. This is the solution that works for me: Apparently, if pip can find a local version of the package, pip will prefer the local versions to remote ones. I even disconnected my computer from the internet and tried it again — when pip … Read more
Option 1: Install as package data The main advantage of placing data files inside the root of your Python package is that it lets you avoid worrying about where the files will live on a user’s system, which may be Windows, Mac, Linux, some mobile platform, or inside an Egg. You can always find the … Read more
My philosophy is that install_requires should indicate a minimum of what you need. It might include version requirements if you know that some versions will not work; but it shouldn’t have version requirements where you aren’t sure (e.g., you aren’t sure if a future release of a dependency will break your library or not). Requirements … Read more
Note: The solution below only works when installing a source distribution zip or tarball, or installing in editable mode from a source tree. It will not work when installing from a binary wheel (.whl) This solution is more transparent: You will make a few additions to setup.py and there is no need for an extra … Read more
Problem: you have 64-bit Python, and a 32-bit installer. This will cause problems for extension modules. The reasons why the installer doesn’t finds Python is the transparent 32-bit emulation from Windows 7. 64-bit and 32-bit programs will write to different parts of the Windows registry. 64-bit: HKLM|HKCU\SOFTWARE\ 32-bit: HKLM|HKCU\SOFTWARE\wow6432node\. This means that the 64-bit Python … Read more
Re: “Do I need a MANIFEST.in? No, you do not have to use MANIFEST.in. Both, distutils and setuptools are including in source distribution package all the files mentioned in setup.py – modules, package python files, README.txt and test/test*.py. If this is all you want to have in distribution package, you do not have to use … Read more
The key is to tell easy_install where the package can be downloaded. In this particular case, it can be found at the url http://github.com/mtai/python-gearman/tarball/master. However, that link by itself won’t work, because easy_install can’t tell just by looking at the URL what it’s going to get. By changing it to http://github.com/mtai/python-gearman/tarball/master#egg=gearman-2.0.0beta instead, easy_install will be … Read more
After digging through the pip issue 3939 linked by @muon in the comments above and then the PEP-508 specification, I found success getting my private repo dependency to install via setup.py using this specification pattern in install_requires (no more dependency_links): install_requires = [ ‘some-pkg @ git+ssh://git@github.com/someorgname/pkg-repo-name@v1.1#egg=some-pkg’, ] The @v1.1 indicates the release tag created on … Read more