public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygport 0.24.0-1
Date: Wed, 22 Mar 2017 20:10:00 -0000	[thread overview]
Message-ID: <20170322201000.Fw-ANp8vZ6eLGReYFkBYDLGoWE-yjkxQygYYx9mEQvU@z> (raw)

The following packages have been uploaded to the Cygwin distribution:

* cygport-0.24.0-1

cygport is the standard method for building and maintaining packages for 
the Cygwin distribution.

This release features many changes in Python packaging:

* The preferred packaging method for Python modules is now 
python-wheel.cygclass.  It can be used for both archful and noarch modules 
to build packages for both Python 2 and 3 automatically.  This requires the 
new python*-pip packages and their dependencies.

* The new python.org.cygclass defines HOMEPAGE and SRC_URI for PyPI-hosted 
sources.

* Python modules in /usr/lib/pythonX.Y are byte-compiled automatically with 
the matching Python interpreter.  Calling python*_optimize without 
arguments is now a no-op, but remains for when a package-specific directory 
(e.g. /usr/share/$NAME) is specified.

* Everything named with a 'python' or 'PYTHON' prefix now uses 'python2' or 
'PYTHON2' instead.  The old names remain for compatibility.

Changes in this release (33):
      kde4: prune kde-l10n file lists
      list_deps: tighten Python module dependency detection
      pkg_dist: correctly obsolete the main package
      kf5: define KDE_INSTALL_SYSCONFDIR, KDE_INSTALL_LOCALSTATEDIR
      python-distutils: run only build, not config
      python3-distutils: run only build, not config
      postinst: automatically byte-compile Python site modules
      python: drop PYTHON_SITELIB default from python_optimize
      python-distutils: drop python_optimize from python_install
      python3: drop PYTHON3_SITELIB default from python3_optimize
      python3-distutils: drop python3_optimize from python3_install
      python.org: new cygclass for downloading from PyPI
      python-distutils: use python.org.cygclass for HOMEPAGE and SRC_URI
      python3-distutils: use python.org.cygclass for HOMEPAGE and SRC_URI
      python2, python2-distutils: new cygclasses to replace unversioned python
      pygtk: update docs wrt upstream status
      list_deps: used versioned python2 names
      python: rework as wrapper for python2.cygclass
      python-distutils: rework as wrapper for python2-distutils.cygclass
      Add check_python2_module, deprecate check_python_module
      prepdoc: add internal hook to auto-install docs for all subpackages
      Fix __fix_shebang usage throughout
      python-wheel: new cygclass for building wheels for Python 2 and 3
      pypy: doc fix
      pypy-distutils: use python.org.cygclass for HOMEPAGE and SRC_URI
      dodoc: simplify doc extension loop, recognize .rst extension
      python3: optimize at both levels for PEP-488
      Update gnuconfig
      python-distutils: inherit python.cygclass for API compatibility
      python2-distutils: set ORIG_PN where NAME=python-*
      python-wheel: accept ctypes wheel names
      python-wheel: ensure clean distutils build dir
      Bump version to 0.24.0

--
Yaakov

                 reply	other threads:[~2017-03-22 20:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170322201000.Fw-ANp8vZ6eLGReYFkBYDLGoWE-yjkxQygYYx9mEQvU@z \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).