From: Adam Dinwoodie <adam@dinwoodie.org>
To: Doug Henderson <djndnbvg@gmail.com>
Cc: Cygwin Apps <cygwin-apps@cygwin.com>
Subject: Re: xlsx2csv package may not be required.
Date: Fri, 17 Mar 2023 09:29:35 +0000 [thread overview]
Message-ID: <20230317092935.gnhy6het67peihf5@lucy.dinwoodie.org> (raw)
In-Reply-To: <CAJ1FpuPbF-t06kMiwwf=i+QztLcMzbbSycb2x2JJ=5E8gWpoWQ@mail.gmail.com>
On Thu, Mar 16, 2023 at 07:58:48PM -0600, Doug Henderson via Cygwin-apps wrote:
> There is a current pure python version of xlsx2csv which runs for many
> versions of Python 2 and Python 3.
>
> It may not be necessary to provide a package for it in cygwin.
> Instead, users may install the pure python package from PYPI
> https://pypi.org/ using pip or another python package manager.
Installing using pip or similar is an option for the vast majority of
packages that are available through the Cygwin installer; by that logic
it wouldn't make sense to provide most of the Python packages we
provide. Which wouldn't be an invalid strategy, but it would be a very
big change in how we handle things!
I think the advantage of using the Cygwin packages is a better
likelihood of packages actually being compatible with Cygwin, rather
than having some weird and unpredictable package dependency issue. A
pure Python xlsx2csv is very unlikely to be affected by that sort of
issue, but providing it as a Cygwin package means users shouldn't need
to even think about whether the package is a pure Python package or not.
next prev parent reply other threads:[~2023-03-17 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 1:58 Doug Henderson
2023-03-17 9:29 ` Adam Dinwoodie [this message]
2023-03-18 16:56 ` marco atzeri
2023-03-22 7:14 ` Jari Aalto
2023-03-22 19:13 ` Brian Inglis
2023-03-22 19:41 ` Brian Inglis
2023-03-24 13:31 ` Jari Aalto
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=20230317092935.gnhy6het67peihf5@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin-apps@cygwin.com \
--cc=djndnbvg@gmail.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).