public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Package request: python-pytest-mock
Date: Thu, 17 Feb 2022 13:05:23 +0000	[thread overview]
Message-ID: <20220217130523.ydsbka2jhqtdbxwc@lucy.dinwoodie.org> (raw)
In-Reply-To: <b9f72870-daed-be58-b2b2-c61c64ff9a43@gmail.com>

On Thu, Feb 17, 2022 at 08:11:31AM +0100, Marco Atzeri wrote:
> On 16.02.2022 12:55, Adam Dinwoodie wrote:
> > On Wed, Feb 16, 2022 at 12:49:05PM +0100, marco atzeri wrote:
> > > On Wed, Feb 16, 2022 at 12:16 PM Adam Dinwoodie  wrote:
> > > > 
> > > > As part of pulling some of the packages I maintain up to date, I've
> > > > discovered some of the test scripts now rely on the pytest-mock module.
> > > > That's not currently packaged for Cygwin; could we make it available?
> > > > 
> > > > I'm happy to add packaging this up to my stack of packages to maintain,
> > > > (although I'm not likely to actually get to packaging it myself for a
> > > > little while) but as most of the Python packages -- and all the
> > > > python-pytest* packages -- are currently maintained by Marco Atzeri, I
> > > > wanted to check if he'd rather add this to his list first.
> > > > 
> > > > Adam
> > > > 
> > > 
> > > I will add, but I suspect it will not be very short term.
> > > My PC is currently not 100% available :-(
> > 
> > Oh no!  If I can help get things started, I'd be very happy to :)
> > 
> 
> I succeded to sneak in the build.
> 
> version 3.7 is up for python 3.7 to 3.9
> 
> Regards
> Marco

Amazing, thank you!

      parent reply	other threads:[~2022-02-17 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 11:16 Adam Dinwoodie
2022-02-16 11:49 ` marco atzeri
2022-02-16 11:55   ` Adam Dinwoodie
2022-02-17  7:11     ` Marco Atzeri
2022-02-17 10:34       ` marco atzeri
2022-02-17 13:05       ` Adam Dinwoodie [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220217130523.ydsbka2jhqtdbxwc@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.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.
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).