| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
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.
|
|
|
|
|
|
| |
bdist_egg ignore the RPM root when building an egg. This version now can
actually run bdist_rpm to completion, although the resulting RPM will
install an egg without a corresponding .pth file.
|
| |
|
| |
|
|
|
|
| |
manual outline.
|
|
|
|
| |
case, and more thoroughness in the --always-copy case.
|
|
|
|
|
| |
incompatible eggs that might have ended up in the distribution directory,
but the "fixed" code was broken.
|
|
|
|
|
| |
(or check out from Subversion) one or more source distributions, without
actually building or installing them (or their dependencies).
|
|
|
|
| |
extensions.
|
|
|
|
|
| |
add ``#egg=project-version`` link support, and docs on how to make your
package available for EasyInstall to find.
|
|
|
|
|
| |
add ``#egg=project-version`` link support, and docs on how to make your
package available for EasyInstall to find.
|
|
|
|
|
|
|
| |
because it isn't necessarily a filesystem path (and hasn't been for some
time now). ``Distribution`` objects now have an ``as_requirement()``
method that returns a ``Requirement`` for the distribution's project name
and version.
|
|
|
|
|
| |
``IMetadataProvider`` interfaces, so you don't need to reference the (no
longer available) ``metadata`` attribute to get at these interfaces.
|
|
|
|
|
|
|
|
|
| |
both have 'project_name' attributes, instead of one having 'name' and the
other 'distname'. Requirements no longer have 'options', they have
'extras'. This is the beginning of the terminology/architecture
refactoring described at:
http://mail.python.org/pipermail/distutils-sig/2005-June/004652.html
|
|
|
|
|
| |
Made ``easy-install.pth`` work in platform-specific alternate site
directories (e.g. ``~/Library/Python/2.x/site-packages``).
|
|
|
|
|
| |
``python -m`` scripts. Misc. fixes for win32.exe support, including
changes to support Python 2.4's changed ``bdist_wininst`` format.
|
|
|
|
| |
EasyInstall act on zip safety flags. Add a lot more docs for setuptools.
|
|
|
|
| |
summary to setuptools doc. Begin work on ``zip_safe`` flag.
|
|
|
|
|
|
|
|
|
| |
script it's running. This avoids it getting confused by projects with
non-standard distribution locations, and projects that may have various
eggs already sitting in their distribution directory. It should probably
also do something like this for the build directory to ensure a clean,
fresh build, but it seems like overkill, since it only affects local
projects, not stuff that EasyInstall downloaded in the first place.
|
|
|
|
|
| |
of its arguments. Fix swapped short option names for --bdist-dir and
--dist-dir in bdist_egg.
|
|
|
|
|
| |
packages managed by EasyInstall. Also, add an option to exclude source
files from .egg distributions.
|
|
|
|
|
|
|
|
| |
will include all files under revision control (CVS or Subversion) in the
current directory, and it will regenerate the list every time you create a
source distribution, not just when you tell it to. This should make the
default "do what you mean" more often than the distutils' default behavior
did, while still retaining the old behavior in the presence of MANIFEST.in.
|
|
|
|
|
|
|
|
| |
installs an ``.egg-link`` pointing to the package's source directory, and
script wrappers that ``execfile()`` the source versions of the package's
scripts. This lets you put your development checkout(s) on sys.path
without having to actually install them. (To uninstall the link, use
use ``setup.py develop --uninstall``.)
|
|
the ``easy_install`` module to ``setuptools.command.easy_install``. Note
that if you were importing or extending it, you must now change your
imports accordingly. ``easy_install.py`` is still installed as a script,
but not as a module.
|