From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Requesting a Python 3.8 build of python-requests
Date: Thu, 23 Jul 2020 12:32:21 +0100 [thread overview]
Message-ID: <AM0PR05MB4898DB49D3DF8C69BDF1BDECE7760@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAB8Xom-hXpC1sm0Y37A1hedLa1-67FDpSwBY0UoGf2=CaGuOLw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1033 bytes --]
On 23/07/2020 12:02, marco atzeri via Cygwin-apps wrote:
> On Thu, Jul 23, 2020 at 11:33 AM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Hello,
>>
>> Who currently maintains python-requests? Marco, if this is you I might
>> have to take you up on your offer and ask you to build a package for
>> Python 3.8 :)
>>
>> If not I guess I'll do a one-time update to build for Python 3.8.
>>
>> Hamish
>>
> Noted,
> I am adopting python packages step by step as I build them
> give me some time as I will need to build some required packages
>
> see @ python37-requests on setup.ini
> requires: ca-certificates python37 python37-chardet python37-idna
> python37-urllib3
>
> and probably some others are needed recursively
Cheers, and yeah absolutely no rush or pressure - we're all volunteers
:). Everything for my GUI seems to be working on Python 3.7 anyway, so I
can just update it for 3.8 later if needs be.
I have some other stuff to fix anyway, I'm expecting it to take a little
while.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-23 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 9:31 Hamish McIntyre-Bhatty
2020-07-23 11:02 ` marco atzeri
2020-07-23 11:32 ` Hamish McIntyre-Bhatty [this message]
2020-07-23 18:00 ` Marco Atzeri
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=AM0PR05MB4898DB49D3DF8C69BDF1BDECE7760@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin-apps@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).