all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Cyril Roelandt <tipecaml@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 28676@debbugs.gnu.org
Subject: [bug#28676] [PATCH 2/4] gnu: Add python-linecache2.
Date: Sun, 8 Oct 2017 05:48:54 +0200	[thread overview]
Message-ID: <44980d57-2540-697a-61c1-e3877fb6c77b@gmail.com> (raw)
In-Reply-To: <20171003143357.GA26590@jasmine.lan>

On 10/03/2017 04:33 PM, Leo Famulari wrote:
> Can you add the details of what this is ported from, and what it's
> ported to? That will make it easier to know when we can remove it later
> on, once everything is updated. And the same for the other backport
> package.

So, both linecache2 and traceback2 are quite poorly documented in this
regard. They seem to be backports of linecache and traceback from Python
3 to Python 2.x, but both these modules existed in Python 2.x, so I'm
not exactly sure of what they do.

To be honest, I do not think anybody uses them in real life: they seem
to only be needed by unittest2 (which was written by the same author).
If it's OK with you, I'd rather leave the description as is, rather than
guessing. WDYT?


Cyril.

  reply	other threads:[~2017-10-08  3:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  1:19 [bug#28677] [PATCH 0/4] Update python2-unittest2 Cyril Roelandt
2017-10-03  1:19 ` [bug#28678] [PATCH 1/4] gnu: python-netaddr: Fix the source URL Cyril Roelandt
2017-10-03  1:19 ` [bug#28676] [PATCH 2/4] gnu: Add python-linecache2 Cyril Roelandt
2017-10-03 14:33   ` Leo Famulari
2017-10-08  3:48     ` Cyril Roelandt [this message]
2017-10-09 19:47       ` Leo Famulari
2017-10-03  1:19 ` [bug#28679] [PATCH 3/4] gnu: Add python-traceback2 Cyril Roelandt
2017-10-03  1:19 ` [bug#28680] [PATCH 4/4] gnu: python2-unittest2: Update to 1.1.0 Cyril Roelandt
2017-10-03 14:34   ` Leo Famulari

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=44980d57-2540-697a-61c1-e3877fb6c77b@gmail.com \
    --to=tipecaml@gmail.com \
    --cc=28676@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.