unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Phil <phil@beadling.co.uk>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Types and builds for mypy
Date: Tue, 25 Oct 2022 19:47:59 -0400	[thread overview]
Message-ID: <87r0yvsbww.fsf@gmail.com> (raw)
In-Reply-To: <87a65ndc0j.fsf@beadling.co.uk> (phil@beadling.co.uk's message of "Sat, 22 Oct 2022 18:05:48 +0100")

Hi Phil,

Phil <phil@beadling.co.uk> writes:

> Thanks for your reply Maxim,
>
> Maxim Cournoyer writes:
>
>
>> Is MyPy the only consumer of Python type annotations?  I think so, but
>> I'm not sure.  If it's the only one, it'd make sense to move mypy and
>> all the annotation types to (gnu packages python-types), I think.
>
> Mypy is certainly a prominent consumer, but you're right - PEP 561 type stub
> packages are also used by PyCharm, pytype, and I've heard CPython can
> use them to compile, to name a few.
>
> So I think my revised opinion is mypy should stay where it is, but I do
> like the idea of keeping all the types in one module?

I'd actually be fine with having mypy in a (gnu packages python-types)
module along its types packages.

[...]

> Cool thanks - leave this with me, I have a working package so can submit
> a patch shortly!

Excellent!

-- 
Thanks,
Maxim


      reply	other threads:[~2022-10-25 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 10:09 Types and builds for mypy Philip Beadling
2022-10-22 13:53 ` Maxim Cournoyer
2022-10-22 17:05   ` Phil
2022-10-25 23:47     ` Maxim Cournoyer [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=87r0yvsbww.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=phil@beadling.co.uk \
    /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).