[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#907914: RFS: elpy/1.24.0-1



Package: sponsorship-requests
Severity: normal

Hi Chris, and dear mentors,

I am looking for a sponsor for my package "elpy".

Package name    : elpy
Version         : 1.24.0-1
URL             : https://github.com/jorgenschaefer/elpy
License         : GPL-3+
Section         : devel

To address the last TODO list submitted for this package: I have not
yet pursued changes to lintian about the Informational message on
"wrong section".  I will ask an Emacsen and Policy team member about
where the appropriate place to pursue this issue would be, because I
believe lintian is currently doing the right thing in providing
Informational-level nagging, as if to say "Are you really sure the
declared section is more appropriate?"  Yes, I am certain that section
"devel" is most appropriate for an IDE addon ;-)

It builds this binary package:

  elpa-elpy  - Emacs Python Development Environment

To access further information about this package, please visit the following URL:

  https://mentors.debian.net/package/elpy

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/e/elpy/elpy_1.24.0-1.dsc

Changes since the last upload:

elpy (1.24.0-1) unstable; urgency=medium

  * New upstream version.
  * Revert "Compress README.rst with gzip before installing" because
    README.rst is only 2.8k and dh_compress already does the right thing
    automatically; that is to say, README.rst is not "larger than 4k in
    size" (dh_compress(1)) and should not be compressed.
  * Exclusively use Python 3 dependencies and configure the use of
    /usr/bin/python3 by default. (Closes: #899212)
  * debian/README.Debian:  Document how Python 2 support is not enabled
    in this Debian package.
  * debian/debian-autoloads.el:
    - Add Debian-specific configuration to default to using Python 3.
    - Document this customisation in README.Debian along with instructions
      on how to revert this when moving between Python 2 and Python 3
      virtualenvs.
    - Additionally unset Elpy's custom PYTHONPATH, which is not needed in
      packages that use dh-python.  Previously Elpy unnecessarily searched
      site-lisp/elpa/elpy-1.23.0 for its associated Python modules.
  * debian/control:
    - Drop python2 dependencies which are no longer needed
      for self-tests to pass.
    - Put ELPA build-dep section before Python one (more alphabetical).
    - Move python3-sphinx build dependency to the section for documentation.
    - Add python3-jupyter-console to Suggests.  The upstream Elpy project
      recommends using Jupyter console for interactive Python.
    - Rely on ${elpa:Depends} and drop explicitly declared ones in bin:pkg.
    - Rely on ${python3:Depends} to generate dependency on python3-flake8.
    - Add build and runtime dependency on flake8, which provides
      /usr/bin/flake8.  This wrapper script is still used in various places,
      and it is part of the flake8 package provided by PyPI/pip.
  * Declare Standards-Version: 4.2.1. (No additional changes required)

 -- Nicholas D Steeves <nsteeves@gmail.com>  Mon, 03 Sep 2018 20:08:24 -0400

elpy (1.23.0-1) unstable; urgency=medium


Regards,
Nicholas D Steeves


Reply to: