phillip.eby  committed 9c400f5

Document 0.6b1 fixes

  • Participants
  • Parent commits 65c8f6c
  • Branches setuptools-0.6

Comments (0)

Files changed (3)

File EasyInstall.txt

+ * Better ambiguity management: accept ``#egg`` name/version even if processing
+   what appears to be a correctly-named distutils file, and ignore ``.egg``
+   files with no ``-``, since valid Python ``.egg`` files always have a version
+   number (but Scheme eggs often don't).
+ * Support ``file://`` links to directories in ``--find-links``, so that
+   easy_install can build packages from local source checkouts.
  * Added automatic retry for Sourceforge mirrors.  The new download process is
    to first just try, then randomly select mirror IPs and
    remove ones that fail, until something works.  The removed IPs stay removed
    for the remainder of the run.
+ * Ignore bdist_dumb distributions when looking at download URLs.
  * Process ``dependency_links.txt`` if found in a distribution, by adding the
    URLs to the list for scanning.
  * Update for changed SourceForge mirror format
  * Fixed not installing dependencies for some packages fetched via Subversion
  * Fixed dependency installation with ``--always-copy`` not using the same
    needed package as the default version of that package.
  * Fixed a problem parsing version numbers in ``#egg=`` links.
  * EasyInstall can now install "console_scripts" defined by packages that use
    ``setuptools`` and define appropriate entry points.  On Windows, console

File pkg_resources.txt

    ``get_build_platform()`` to work around a Mac versioning problem that caused
    the behavior of ``compatible_platforms()`` to be platform specific.
+ * Fix entry point parsing when a standalone module name has whitespace
+   between it and the extras.
  * Added ``ExtractionError`` and ``ResourceManager.extraction_error()`` so that
    cache permission problems get a more user-friendly explanation of the

File setuptools.txt

     has an ``additional_tests()`` function, it is called and the results are
     added to the tests to be run.  If the named suite is a package, any
     submodules and subpackages are recursively added to the overall test suite.
     Specifying this argument enables use of the `test`_ command to run the
     specified test suite, e.g. via `` test``.  See the section on the
     `test`_ command below for more details.
 Note that you can also apply setuptools commands to non-setuptools projects,
 using commands like this::
    python -c "import setuptools; execfile('')" develop
 That is, you can simply list the normal setup commands and options following
   with the absence of needed programs (i.e., ones belonging to the revision
   control system itself.  It *may*, however, use ``distutils.log.warn()`` to
   inform the user of the missing program(s).
 Subclassing ``Command``
 Release Notes/Change History
+ * Strip ``module`` from the end of compiled extension modules when computing
+   the name of a ``.py`` loader/wrapper.  (Python's import machinery ignores
+   this suffix when searching for an extension module.)
  * Added ``test_loader`` keyword to support custom test loaders