From: ludo@gnu.org (Ludovic Courtès)
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: 31282@debbugs.gnu.org
Subject: [bug#31282] [PATCH 1/2] gnu: Add python-parso.
Date: Mon, 30 Apr 2018 14:34:31 +0200 [thread overview]
Message-ID: <87efiwzxd4.fsf@gnu.org> (raw)
In-Reply-To: <BLUPR16MB0500BFB454ECE1E7F0C9C1DC928D0@BLUPR16MB0500.namprd16.prod.outlook.com> (Fis Trivial's message of "Fri, 27 Apr 2018 06:58:04 +0000")
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
Fis Trivial <ybbs.daans@hotmail.com> skribis:
> * gnu/packages/python.scm (python-parso, python2-parso): New variables.
Applied with the changes below, thanks!
Ludo'.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 836 bytes --]
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 7fe27bd17..f23deb57e 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -13160,12 +13160,11 @@ time-based (TOTP) passwords.")
(native-inputs
`(("python-pytest" ,python-pytest)))
(build-system python-build-system)
- (home-page
- "https://github.com/davidhalter/parso")
+ (home-page "https://github.com/davidhalter/parso")
(synopsis "Python Parser")
(description "Parso is a Python parser that supports error recovery and
round-trip parsing for different Python versions (in multiple Python versions).
-Parso is also able to list multiple syntax errors in your python file.")
+Parso is also able to list multiple syntax errors in your Python file.")
(license license:expat)))
(define-public python2-parso
prev parent reply other threads:[~2018-04-30 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 6:58 [bug#31282] [PATCH 1/2] gnu: Add python-parso Fis Trivial
2018-04-27 7:03 ` [bug#31282] [PATCH 2/2] gnu: python-jedi: Update to 0.12.0, enable tests Fis Trivial
2018-04-30 12:37 ` Ludovic Courtès
2018-04-30 12:34 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efiwzxd4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31282@debbugs.gnu.org \
--cc=ybbs.daans@hotmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).