From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>,
Brian Inglis <Brian.Inglis@Shaw.ca>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: ITA xlsx2csv (was Re: python2 removal)
Date: Thu, 16 Mar 2023 18:57:15 +0000 [thread overview]
Message-ID: <2de90be0-8871-7390-950c-f65c2514e65e@dronecode.org.uk> (raw)
In-Reply-To: <efc4f3db-47e8-1743-1bb9-5966e74b247e@Shaw.ca>
On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote:
> On 2023-03-16 07:29, Jon Turney wrote:
>
>> The critical piece of data I'm missing here is which of these is true:
>> a) This package contains a script with a python shebang. The current
>> version doesn't work when python is python3, so an upgrade is needed
>> to continue working when python2 is removed, or
>> b) This package contains a script with a python shebang. The current
>> version will continue to work when python is python3.
>
> Unfortunately only a generic cygbuild sh script is supplied with the
> package - does nothing but complain without some other "magic" script or
> data! ;^>
> Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027
> from 0.11+20120814.
>
> $ sed 1q xlsx2csv.py
> #!/usr/bin/env python
>
> Does not work with python3, nor after running 2to3 fixes - see attached
> logs - IANAPythonista
>
> Anyway pylint was not useful compared to 2to3 - see attached pylint
> before and after 2to3 logs compared to 2to3 log.
This is not an unequivocal answer to my question.
It sounds like you are saying "even the most recent version of xlsx2cvs
doesn't work with python3", in which case the only sane option is to
remove this package when python2 is removed.
Is that what you mean? If not, what do you mean?
Please answer with a single sentence.
next prev parent reply other threads:[~2023-03-16 18:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:52 python2 removal Jon Turney
2023-01-15 19:31 ` Ken Brown
2023-01-16 12:49 ` Jon Turney
2023-01-16 14:22 ` Ken Brown
2023-01-16 12:49 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
2023-02-25 16:51 ` Adam Dinwoodie
2023-02-26 11:56 ` Jon Turney
2023-04-30 18:25 ` Jon Turney
2023-04-30 20:32 ` Adam Dinwoodie
2023-05-01 17:53 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
[not found] ` <003a01d94a86$750f4b70$5f2de250$@samsung.com>
2023-02-27 13:36 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
2023-03-07 17:27 ` Jon Turney
2023-01-17 2:27 ` David Rothenberger
2023-03-14 19:16 ` Jon Turney
2023-03-14 19:17 ` Jon Turney
2023-03-15 12:56 ` Brian Inglis
2023-03-15 16:46 ` marco atzeri
2023-03-16 13:29 ` ITA (was Re: python2 removal) Jon Turney
2023-03-16 15:53 ` ITA xlsx2csv " Brian Inglis
2023-03-16 18:57 ` Jon Turney [this message]
2023-03-16 21:12 ` Brian Inglis
2023-03-22 7:36 ` Jari Aalto
2023-03-22 16:23 ` Jon Turney
2023-04-02 15:47 ` python2 removal Jon Turney
2023-04-02 15:55 ` Jon Turney
2023-06-01 16:54 ` Jon Turney
2023-04-02 16:00 ` Jon Turney
2023-04-03 1:08 ` marco atzeri
2023-04-11 6:49 ` Marco Atzeri
2023-06-04 19:17 ` Jon Turney
2023-07-02 14:30 ` Jon Turney
2023-07-07 18:54 ` Marco Atzeri
2023-07-09 16:50 ` Jon Turney
2024-01-18 19:31 ` Jon Turney
2024-01-18 19:40 ` Jon Turney
2024-01-19 18:23 ` Hamish McIntyre-Bhatty
2024-04-10 19:19 ` Hamish McIntyre-Bhatty
2024-04-11 12:23 ` Jon Turney
2023-06-11 18:06 ` 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=2de90be0-8871-7390-950c-f65c2514e65e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@Shaw.ca \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--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).