| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
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
|
|
|
|
| |
a specified list of server glob patterns.
|
|
|
|
|
|
|
|
|
| |
means that people are finally doing enough things with setuptools to
have real-life version conflict scenarios. Luckily, the fix is trivial:
use breadth-first instead of depth-first dependency processing, which I
thought we were already doing anyway, but weren't. And we were giving
precedence to already-installed packages, which means upgrades didn't
work so well.
|
|
|
|
|
|
|
| |
thereby confusing the import process. Scripts are now generated with a
suffix of the form '-script.py' to avoid conflicts. (The .exe's are still
generated without the '-script' part, so you don't have to type it.)
Thanks to Matthew R. Scott for reporting the problem.
|
|
|
|
| |
builder script.
|
|
|
|
| |
"normal" #! wrappers for GUI scripts on other platforms.
|
|
|
|
|
|
|
|
|
|
|
| |
installed applications will not have their eggs overridden by packages
installed locally on sys.path. This should also make things work a bit
better for "traditional" non-root Python setups on Unixy operating
systems. See:
http://mail.python.org/pipermail/distutils-sig/2005-September/005164.html
for more details.
|
|
|
|
|
|
|
|
|
|
| |
extension elsewhere" problem, while also bypassing the need for PATHEXT
on Windows, and in fact the need to even write script files at all, for
any platform. Instead, you define "entry points" in your setup script,
in this case the names of the scripts you want (without extensions) and
the functions that should be imported and run to implement the scripts.
Setuptools will then generate platform-appropriate script files at
install time, including an .exe wrapper when installing on Windows.
|
|
|
|
| |
especially important for RPMs with scripts.
|
|
|
|
| |
some bdist_* targets install to a pseudo-root where stuff might not exist.
|
| |
|
|
|
|
|
| |
do directory tree removals only if isdir() and not islink(), and use
unlink() in all other cases.
|
|
|
|
|
| |
.pth files and legacy packages possibly being symlinks, and ensure that
overwrites don't follow the symlink.
|