From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ANNOUNCEMENT] cygport 0.36.1-1
Date: Tue, 11 Apr 2023 06:14:06 +0200 [thread overview]
Message-ID: <ff5e11d3-7743-39fb-70f6-e5072e76041f@gmail.com> (raw)
In-Reply-To: <faebea23-d7ca-f472-9662-aa99f5bc08ac@dronecode.org.uk>
On 26.03.2023 18:43, Jon Turney wrote:
> On 11/03/2023 20:15, Marco Atzeri via Cygwin-apps wrote:
>> On 11.03.2023 17:29, Jon Turney via Cygwin wrote:
>>>
>>> The following packages have been uploaded to the Cygwin distribution:
>>>
>>> * cygport-0.36.1-1
>>>
>>
>> Hi Jon,
>>
>> I was a bit too late...
>
> No problem, I can always make more releases!
>
>> Updating the python 3.[89] subpackages, I finally hit
>> a case where setup.py and setup.cfg are missing as obsolete.
>>
>> Attached patch solved the issue and allowed to build
>> python-platformdirs-3.1.1-1
>
> Thanks.
>
> I'm not sure if always emitting a warning if pyproject.toml is missing
> is good idea, so I might do a bit of tweaking, but I applied this patch.
>
> (as that will probably warn if you ever try to build an old version of a
> project, which is still perfectly buildable due to having a setup.py)
>
Hi Jon,
what about his form ?
if [ ! -e pyproject.toml ]
then
warning "No pyproject.toml (PEP 518) detected in source tree"
warning "Trying previous Distutils method."
if [ ! -e setup.py ] && [ ! -e setup.cfg ]
then
error "No Python Distutils module neither pyproject.toml
(PEP 518) detected in source tree"
fi
fi
I would any some version of it released before I upload the git source
that has only pyproject.toml.
Otherwise scullywag will fail the build.
Regards
Marco
next prev parent reply other threads:[~2023-04-11 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.35193db5-ad95-ce9d-53fe-4ed535da8279@dronecode.org.uk>
2023-03-11 20:15 ` Marco Atzeri
2023-03-26 16:43 ` Jon Turney
2023-04-11 4:14 ` Marco Atzeri [this message]
2023-04-11 18:54 ` Jon Turney
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=ff5e11d3-7743-39fb-70f6-e5072e76041f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.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.
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).