From: wednesday <jessejohngildersleve@zohomail.eu>
To: 35193@debbugs.gnu.org
Cc: wednesday <jessejohngildersleve@zohomail.eu>
Subject: [bug#35193] [PATCH v2 0/3] Updating and fixing mypy packages
Date: Tue, 30 Apr 2019 16:29:11 +0100 [thread overview]
Message-ID: <20190430152914.13616-1-jessejohngildersleve@zohomail.eu> (raw)
In-Reply-To: <clcw9plVchj9b2Re4ypNFSB9-744wR__yl_rGITHVjSpti_knLYaKGtf94hTTll1Ss-hgoQY96M27EVB8iQuLfihg11ddVFLTBNbRGWXKIE=@protonmail.com>
In these patches I updated the packages related to mypy, as well as mypy.
In addition to that I fixed an issue with python-mypy-extensions that was
causing mypy to fail when checking python3.
Also these patches were formatted and sent with git send-email, unlike
the other ones, so hopefully you'll have an easier time applying them.
wednesday (3):
gnu: Add python-typed-ast
gnu: Add python-mypy-extensions
gnu: Add python-mypy
gnu/packages/python-xyz.scm | 76 +++++++++++++++++++++++++++++++++++++
1 file changed, 76 insertions(+)
--
2.21.0
next prev parent reply other threads:[~2019-04-30 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 13:44 [bug#35193] [PATCH 0/3] Add python-mypy and required packages JesseJohnGildersleve
2019-04-08 14:20 ` [bug#35193] [PATCH 1/3] Add python-typed-ast JesseJohnGildersleve
2019-04-08 14:21 ` [bug#35193] [PATCH 2/3] Add python-mypy-extensions JesseJohnGildersleve
2019-04-08 14:23 ` [bug#35193] [PATCH 3/3] Add python-mypy JesseJohnGildersleve
2019-04-30 15:29 ` wednesday [this message]
2019-04-30 15:29 ` [bug#35193] [PATCH v2 1/3] gnu: Add python-typed-ast wednesday
2019-04-30 15:29 ` [bug#35193] [PATCH v2 2/3] gnu: Add python-mypy-extensions wednesday
2019-04-30 15:29 ` [bug#35193] [PATCH v2 3/3] gnu: Add python-mypy wednesday
2019-06-27 14:11 ` swedebugia
2021-04-03 3:20 ` bug#35193: [PATCH 0/3] Add python-mypy and required packages Maxim Cournoyer
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=20190430152914.13616-1-jessejohngildersleve@zohomail.eu \
--to=jessejohngildersleve@zohomail.eu \
--cc=35193@debbugs.gnu.org \
/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).