| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
Scripts installed with ``bdist_wininst`` will always use ``#!python.exe`` or
``#!pythonw.exe`` as the executable name (even when built on non-Windows
platforms!), and the wrappers will look for the executable in the script's
parent directory (which should find the right version of Python).
(backport from trunk)
|
|
|
|
|
|
|
| |
Unfortunately, bdist_wininst doesn't fix up #! lines, so python.exe or
pythonw.exe have to be on PATH for generated scripts to work. This
could probably be fixed up with a post-install script, but that's a
job for another day. (backport from trunk)
|
|
|
|
|
| |
mirror system now works well for non-browser downloads.
(backport from trunk)
|
|
|
|
|
| |
has a space in it (e.g., the user installed Python to a ``Program
Files`` directory). (backport from trunk)
|
|
|
|
|
|
| |
``develop`` and the source directory is a subdirectory of the installation
target directory.
(backport from trunk)
|
|
|
|
|
| |
further refine download/retry algorithm.
(backport from trunk)
|
|
|
|
|
|
|
| |
to an .egg file to allow it to be run as a script on Unix-ish platforms.
(This is mainly so that setuptools itself can have a single-file installer
on Unix, without doing multiple downloads, dealing with firewalls, etc.)
(Backport from trunk)
|
|
|
|
| |
(backport from trunk)
|
| |
|
|
|
|
|
|
| |
contains non-ASCII characters, to prevent deprecation warnings about an
unspecified encoding when the script is run.
(backport from trunk)
|
|
|
|
| |
using --editable.
|
|
|
|
| |
or directory is deleted/overwritten.
|
|
|
|
|
| |
http://mail.python.org/pipermail/distutils-sig/2006-June/006359.html
(merge from trunk)
|
|
|
|
|
| |
directories.
(merge from trunk)
|
|
|
|
| |
(merge from trunk)
|
|
|
|
| |
name begins with ``import`` doesn't cause a syntax error.
|
|
|
|
| |
--multi-version. (backport from trunk)
|
|
|
|
|
|
|
| |
``PYTHONPATH`` directory with ``--multi-version``, unless an
``easy-install.pth`` file is already in use there.
(Bugfix merge from 0.7 trunk)
|
| |
|
|
|
|
| |
draft of a patch.
|
|
|
|
|
| |
lets easy_install handle pywin32... well, almost. You still have to
deal with the "system" DLLs yourself.
|
|
|
|
| |
but different contents.
|
|
|
|
|
| |
same directory as the ``.pth`` file. This maximizes portability of the
target directory when building applications that contain eggs.
|
|
|
|
|
| |
the installation of any ``__init__.py`` files for namespace packages, and
adding a special ``.pth`` file to create a working package in ``sys.modules``.
|
|
|
|
|
|
|
|
|
| |
the front of sys.path, in an order consistent with where they came from,
making EasyInstall seamlessly co-operate with system package managers.
The ``--delete-conflicting`` and ``--ignore-conflicts-at-my-risk`` options
are now no longer necessary, and will generate warnings at the end of a
run if you use them.
|
|
|
|
| |
--multi-version so that '.' doesn't have to support .pth files.
|
|
|
|
| |
displaying the "extras" that can be added to a package.
|
|
|
|
| |
a ' ' in its name.
|
|
|
|
|
| |
for ``.pth`` file support, and directory writability/existence checks. This
should virtually eliminate the need to set or configure ``--site-dirs``.
|
|
|
|
| |
unfortunately kludgy fashion.
|
| |
|
|
|
|
|
| |
should now "just work" if you're using a PYTHONPATH target, and if it
can't "just work", you get helpful instructions and doc links.
|
|
|
|
|
| |
accomplish anything useful. This one should, but it needs testing by
someone who actually has a Fedora 64-bit x86 setup.
|
| |
|
|
|
|
|
| |
/usr/lib64 patches on 64-bit Fedora) will have a better chance of
working "out of the box".
|
|
|
|
|
|
|
|
| |
directories as early as possible, but now only directories and direct
archive links are scanned immediately. URLs are not retrieved unless a
package search was already going to go online due to a package not being
available locally, or due to the use of the ``--update`` or ``-U``
option. Also, fixed the ``develop`` command ignoring ``--find-links``.
|
|
|
|
|
|
|
| |
since they can't be reliably copied. Note that this may cause EasyInstall
to choose an older version of a package than what you expected, or it may
cause downloading and installation of a fresh version of what's already
installed.
|
| |
|
|
|
|
|
| |
``--install-dir``, and ``--script-dir`` options, whether on the command
line or in configuration files.
|
| |
|
|
|
|
|
|
|
|
| |
as long as you include an ``#egg=name-version`` suffix on the URL, or if
the ``.py`` file is listed as the "Download URL" on the project's PyPI
page. This allows third parties to "package" trivial Python modules
just by linking to them (e.g. from within their own PyPI page or
download links page).
|
|
|
|
|
| |
option when installing generated scripts using the
--single-version-externally-managed option.
|
|
|
|
|
|
|
|
|
|
|
| |
format. Running ``bdist_wininst`` on a setuptools-based package wraps the
egg in an .exe that will safely install it as an egg (i.e., with metadata
and entry-point wrapper scripts), and ``easy_install`` can turn the .exe
back into an ``.egg`` file or directory and install it as such.
At this point, it should also be possible to "system package" any egg,
complete with wrapper scripts, and at least bdist_wininst works now.
More testing is needed for at least bdist_dumb and bdist_rpm.
|
|
|
|
|
| |
can be used by the future install_scripts command to install entry point
scripts in "legacy" mode.
|
|
|
|
|
|
|
| |
will now recognize when a bdist_wininst .exe wraps a .egg-info style
package, and reconstitute it correctly, maintaining the original zip
safety flag, if applicable. This still needs support for entrypoint
scripts, though, as does the install_scripts command.
|
|
|
|
|
| |
options, as this was causing some problems with ``setup.py install``
ignoring global site-dirs settings.
|
|
|
|
| |
"baskets") when they weren't explicitly listed in the ``.pth`` file.
|
|
|
|
| |
shutil.rmtree from 2.4 directly into easy_install.py.
|
|
|
|
| |
(e.g. "setup.py install", or "easy_install somefile/someurl").
|
|
|
|
|
|
|
|
|
|
| |
* Fixed not installing dependencies for some packages fetched via Subversion
* Fixed dependency installation with ``--always-copy`` not using the same
dependency resolution procedure as other operations.
* Fixed not fully removing temporary directories on Windows, if a Subversion
checkout left read-only files behind
|