| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
added support for the provides, requires, and obsoletes metadata fields
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This support was only a first cut, and doesn't deserve to be in
a released version (where we have to support it in an ongoing
manner)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
scripts without modifying either the distutils installation or the
setup.py scripts of packages with which the new commands will be used.
Specifically, an option is added to distutils that allows additional
packages to be searched for command implementations in addition to
distutils.command. The additional packages can be specified on the
command line or via the installation or personal configuration files
already loaded by distutils.
For discussion, see the thread starting with:
http://mail.python.org/pipermail/distutils-sig/2004-August/004112.html
This closes SF patch #102241.
|
| |
|
|
|
|
|
|
|
| |
This is basically the support for package data from Phillip Eby's
setuptools package. I've changed it only to fit it into the core
implementation rather than to live in subclasses, and added
documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requires and provides. requires is a sequence of strings, of the
form 'packagename-version'. The dependency checking so far merely
does an '__import__(packagename)' and checks for packagename.__version__
You can also leave off the version, and any version of the package
will be installed.
There's a special case for the package 'python' - sys.version_info
is used, so
requires= ( 'python-2.3', )
just works.
Provides is of the same format as requires - but if it's not supplied,
a provides is generated by adding the version to each entry in packages,
or modules if packages isn't there.
Provides is currently only used in the PKG-INFO file. Shortly, PyPI
will grow the ability to accept these lines, and register will be
updated to send them.
There's a new command 'checkdep' command that runs these checks.
For this version, only greater-than-or-equal checking is done. We'll
add the ability to specify an optional operator later.
|
|
|
|
|
| |
suggested approach to dealing with it isn't a good one; we need a
better general purpose config reader, not a distutils-specific reader
|
|
|
|
| |
From SF patch #852334.
|
|
|
|
| |
This patch makes it work again.
|
| |
|
|
|
|
| |
Add 'classifiers' keyword to DistributionMetadata
|
|
|
|
| |
suggested by PEP 291.
|
|
|
|
| |
is often out of date
|
| |
|
|
|
|
|
|
|
|
|
|
| |
arguments, triggering a warning instead of raising an exception. (In
1.5.2/2.0, it will print to stderr.)
Bugfix candidate for all previous versions. This changes behaviour,
but the old behaviour wasn't very useful. If Distutils version X+1
adds a new keyword argument, using the new keyword means your setup.py
file won't work with Distutils version X any more.
|
|
|
|
|
| |
Note that distutils.core.DEBUG still works if client code uses it, but
the core code avoids circular references by using distutils.debug.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a conservative version of SF patch 504889. It uses the log
module instead of calling print in various places, and it ignores the
verbose argument passed to many functions and set as an attribute on
some objects. Instead, it uses the verbosity set on the logger via
the command line.
The log module is now preferred over announce() and warn() methods
that exist only for backwards compatibility.
XXX This checkin changes a lot of modules that have no test suite and
aren't exercised by the Python build process. It will need
substantial testing.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
invalid filenames on Windows when building without specifying a
version number in the setup script.
See also
http://mail.python.org/pipermail/distutils-sig/2001-November/002656.html
Bugfix candidate.
|
| |
|
| |
|
|
|
|
|
| |
Use construction-syntax for an exception to make the argument easier
to read.
|
|
|
|
|
|
|
| |
though 'licence' is still supported for backward-compatibility
(Should I add a warning to get_licence(), or not bother?)
Also fixes an UnboundLocalError noticed by PyChecker
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
along with options to print them.
Add a finalize_options() method to Distribution to do final processing
on the platform and keyword attributes
Add DistributionMetadata.write_pkg_info() method to write a PKG-INFO file
into the release tree.
|
| |
|
|
|
|
|
| |
to the Distutils-SIG and archived at
http://mail.python.org/pipermail/distutils-sig/2000-November/001755.html
|
|
|
|
|
| |
use it to generate a dialog for users to specify the command-line (because
providing a command-line with MacPython is so awkward).
|
| |
|
|
|
|
| |
(was crashing on any boolean command-line option!).
|
| |
|
|
|
|
| |
than rolling our own with fancy_getopt's 'longopt_xlate' global.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* options can now be spelled "foo-bar" or "foo_bar" (handled in
'parse_config_files()', just after we parse a file)
* added a "[global]" section so there's a place to set global
options like verbose/quiet and dry-run
* respect the "negative alias" dictionary so (eg.) "quiet=1" is
the same as "verbose=0" (this had to be done twice: once in
'parse_config_file()' for global options, and once in
'_set_command_options()' for per-command options)
* the other half of handling boolean options correctly: allow
commands to list their boolean options in a 'boolean_options'
class attribute, and use it to translate strings (like "yes", "1",
"no", "0", etc) to true or false
|
| |
|
|
|
|
|
|
| |
the command's sub-commands as well (off by default). This is essential if
we want to be be able to run (eg.) "install" twice in one run, as happens
when generating multiple built distributions in one run.
|
|
|
|
|
|
|
|
| |
Changed 'core.setup()' so it sets them to reasonable defaults.
Tweaked how the "usage" string is generated: 'core' now provides
'gen_usage()', which is used instead of 'USAGE'.
Modified "build_py" and "sdist" commands to refer to
'self.distribution.script_name' rather than 'sys.argv[0]'.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
values that "--foo" can take for various commands: eg. what formats for
"sdist" and "bdist", what compilers for "build_ext" and "build_clib".
I have *not* reviewed this patch; I'm checking it in as-is because it also
fixes a paper-bag-over-head bug in bdist.py, and because I won't have
time to review it properly for several days: so someone else can
test it for me, instead!
|
|
|
|
|
| |
and call it "distutils.cfg" instead of "pydistutils.cfg" (personal
config files are still ".pydistutils.cfg" or "pydistutils.cfg", though).
|
|
|
|
|
|
|
|
| |
Look for personal config file in /home/greg on Windows, too: users will have
to set /home/greg to use this, so it's not something that many people will
use. But if python-dev comes up with the "right way" to divine a
home directory on Windows, we can use that to set /home/greg and poof! --
personal Distutils config files on Windows.
|
|
|
|
| |
command being reinitialized to false.
|