elpy 1.32.0-1 source package in Ubuntu

Changelog

elpy (1.32.0-1) unstable; urgency=medium

  [ Salman Mohammadi ]
  * d/control: add python3-sphinx-rtd-theme as a build dependency

  [ Nicholas D Steeves ]
  * Add missing newline to patch series.
  * Add ${sphinxdoc:Depends} to elpa-elpy's Depends.  This installs the
    rtd-theme, which must be a Depends and not a Recommends.  This will also
    install libjs-sphinxdoc as a hard dep, so drop it from Recommends.
  * New upstream release.
  * Rebase patch series onto upstream 1.32.0.
  * Drop 0002-Add-script-to-benchmark-tests.patch which is a commit that
    is present in this release.
  * ert-helper.el: Upstream fixed bugs in scripts/elpy-test-benchmark.el
    which were causing tests to fail due to an unclean test environment,
    so it became possible to drop the (prog1 FIRST BODY) form that was
    used to run tests first.  Also, this means it became possible to move
    (ert-run-tests-batch-and-exit) to the position of the final expression,
    which is what dh-elpa requires.  See Bug #941330 for more info.
  * debian-autoloads.el: Set elpy-rpc-virtualenv-path to "'system".
    Upstream has moved to a default where everything is installed to a
    virtualenv using pip, which is incompatible with Debian Policy.  This
    configuration key restores the previous behaviour of using system
    Python packages by default.
  * rules: Activate ELPY_TEST_DONT_USE_VIRTUALENV, because self-tests and
    autopkgtests test virtualenv creation using pip rather than the
    package as-installed, even when elpy-rpc-virtualenv-path is set to
    "'system".
  * The change above doesn't solve to autopkgtest case, and using
    ert-helper.el doesn't work, so add
    0005-test-helper.el-uniquivocally-set-elpy-test-dont-use-.patch.  It
    is unclear whether this is an upstream bug or a dh-elpa bug.
  * debian-autoloads.el: Add "-E" to python-shell-interpreter args, to
    "Ignore environment variables like PYTHONPATH and PYTHONHOME that
    modify the behavior of the interpreter." (man python3(1)).
  * Disable the execution of benchmarks from ert-runner.el (which is
    called from dh-elpa).  See comment in ert-runner.el for rationale.  It
    is unclear whether these fail due to an upstream Elpy, Emacs, or
    dh-elpa bug.  See https://github.com/jorgenschaefer/elpy/issues/1724
    for more info.  Help would be appreciated!

  [ Salman Mohammadi and Nicholas D Steeves ]
  * Add 0004-docs-conf.py-build-the-documentation-using-sphinx_rt.patch to
    build the documentation using the sphinx_rtd_theme.
  * d/control: Change python3-jupyter-console Suggests to jupyter-console,
    because python3-jupyter-console does not provide
    /usr/bin/jupyter-console, which Elpy requires in order to use this
    functionality.
  * d/control: Add ipython3 to Suggests, but not as an alternative to
    jupyter-console.  IPython can also be configured to be used with Elpy
    as an interactive Python shell.

 -- Nicholas D Steeves <email address hidden>  Thu, 09 Jan 2020 16:22:02 -0700

Upload details

Uploaded by:
Debian Emacsen team
Uploaded to:
Sid
Original maintainer:
Debian Emacsen team
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Focal: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
elpy_1.32.0-1.dsc 2.4 KiB be7d54468f87ac2dfae8f3912a3402f4e2d575ad028c2d5bb7142110738fb51d
elpy_1.32.0.orig.tar.xz 133.9 KiB 58495402002e014ff96a1d810abc72703a86abbd7e591e7057425bdf841a05c6
elpy_1.32.0-1.debian.tar.xz 10.1 KiB 473eaaa93b1bbb21f1cb57e9396f8d78fa7de6d34c106d89694543d9d5dd9aec

Available diffs

No changes file available.

Binary packages built by this source

elpa-elpy: Emacs Python Development Environment

 The Emacs Lisp Python Environment in Emacs
 .
 Elpy is an Emacs package that brings powerful Python editing to
 Emacs. It combines a number of existing Emacs packages, and is
 written in Emacs Lisp as well as Python.
 .
 Features:
   * Navigation by code indentation and code definition.
   * Move the current region as a code block.
   * Treat a working tree as a coherent project; search for files,
     code, or text within the project.
   * Interact with Python interpreters and test runners.
   * Browse the Python built-in documentation.
   * Refactor code and symbols.