| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
non-Windows platforms, due to distutils not handling manifest file line
endings correctly. (backport from trunk)
|
|
|
|
| |
egg_info failures on new, uncommitted SVN directories.
|
|
|
|
| |
(backport from trunk)
|
|
|
|
| |
(backport from trunk)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
sets ``egg_info`` options such that they produce an identical version number
to the source distribution's version number. (Previously, the default
version number could be different due to the use of ``--tag-date``, or if
the version was overridden on the command line that built the source
distribution.)
(backport from trunk)
|
| |
|
|
|
|
|
| |
appear only if you are actually a source distribution.
(backport from trunk)
|
|
|
|
|
| |
command, to allow suppressing tags configured in ``setup.cfg``.
(backports from trunk)
|
|
|
|
| |
draft of a patch.
|
|
|
|
| |
(i.e., when it didn't exist prior to egg_info being run).
|
|
|
|
| |
occur while reading it.
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
in it, but warn about it and refuse to run "develop" until the existing
directory is renamed. This should allow older source distributions and
checkouts to keep working with 0.6a9.
|
|
|
|
|
| |
you must rename any existing .egg-info directory inside a project that
has a '-' in it!
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
distribution.
|
|
|
|
|
|
|
| |
create source distributions. ``MANIFEST.in`` is still read and processed,
as are the standard defaults and pruning. But the manifest is built inside
the project's ``.egg-info`` directory as ``SOURCES.txt``, and it is rebuilt
every time the ``egg_info`` command is run.
|
|
|
|
|
|
|
|
| |
sdist distributions to support building an sdist from an sdist (which the
bdist_rpm command requires). This will also be the basis for enhanced
package data support, that will allow optionally using the manifest to
identify package data files instead of having separate manual identification
of the data files.
|
|
|
|
|
|
|
|
|
|
|
|
| |
``.egg-info/PKG-INFO`` under revision control and put the project's source
code directly in the project directory. If such a package had any
requirements that get processed before the ``egg_info`` command can be run,
the setup scripts would fail with a "Missing 'Version:' header and/or
PKG-INFO file" error, because the egg runtime interpreted the unbuilt
metadata in a directory on ``sys.path`` (i.e. the current directory) as
being a corrupted egg. Setuptools now monkeypatches the distribution
metadata cache to pretend that the egg has valid version information, until
it has a chance to make it actually be so (via the ``egg_info`` command).
|
|
|
|
|
|
|
|
|
| |
revision number from ``PKG-INFO`` in case it is being run on a
source distribution of a snapshot taken from a Subversion-based
project. That is, if a project builds an sdist with
--tag-svn-revision in setup.cfg, then the built sdist will
create binaries with the same version number as the checkout
that was used to create the sdist.
|
|
|
|
|
|
|
|
|
|
|
| |
was trying to have setuptools fix distutils' broken filename handling that
assumes people haven't put punctuation in their distribution names,
including '-' (which prevents unambiguous parsing of distribution names).
However, bdist_rpm's attempt to guess a source distribution's filename
isn't compatible with this fix, without making other changes. I decided
therefore to drop the fixes for the sake of backward compatibility, but
monkeypatch bdist_rpm so that it runs "egg_info" first, to ensure that any
--tag-svn-revision or other tagging options take effect.
|
|
|
|
|
| |
revision number. (Christopher Lenz reported that svn info's output is
different in non-English locales.)
|
|
|
|
| |
Also fixed a few bugs.
|
|
|
|
|
|
| |
written to EGG-INFO. Extensible applications and frameworks can thus make
it possible for plugin projects to supply setup() metadata that can then
be used by the application or framework.
|
|
|
|
|
|
| |
can be plugged in at setup() time to define new setup() arguments or
distutils commands. This allows modularization and reuse of distutils
extensions in a way that was previously not possible.
|
|
|
|
|
|
| |
Change setuptools to discover setup commands using an entry point group
called "distutils.commands". Thanks to Ian Bicking for the suggestion that
led to designing this super-cool feature.
|
|
|
|
|
| |
support for obtaining project-level resources by making get_provider()
accept Requirement objects.
|
|
|
|
| |
highest revision number for the project as a whole.
|
|
|
|
| |
summary to setuptools doc. Begin work on ``zip_safe`` flag.
|
|
|
|
|
| |
packages managed by EasyInstall. Also, add an option to exclude source
files from .egg distributions.
|
|
|
|
| |
number for better readability.
|
|
|
|
|
|
|
|
| |
forms of the distribution name and version, so that distribution files will
be generated with parseable names (i.e., ones that don't include '-' in the
name or version). Also, this means that if you use the various ``--tag``
options of "egg_info", any distributions generated will use the tags in the
version, not just egg distributions.
|
|
|
|
|
|
| |
``--tag-build`` on the "egg_info" command, so that you can make tagged
revisions compare *lower* than the version specified in setup.py (e.g. by
using ``--tag-build=dev``).
|
|
just creates or updates the "projectname.egg-info" directory, without
building an egg. It's used by the ``bdist_egg`` command now, and will be
used by the ``test`` and ``develop`` commands later on.
|