xlsx2csv package may not be required.

[Jari Aalto]

On 2023-03-18 17:56, marco atzeri via Cygwin-apps wrote:
> On Fri, Mar 17, 2023 at 10:29 AM Adam Dinwoodie via Cygwin-apps
> <cygwin-apps@cygwin.com> wrote:
> >
> > 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.
> 
> 
> I agree with Adam.
> I would have no problem to release the python package no if not for
> the problem to the laptop
> 
> I guess one month from now I will be able to be operative again
> (assuming the target supplier of the laptop https://frame.work/ will
> not have delivery problem)

I agree, it's better to have native Python package which is more
likely to be kept up to date by the upstream.

So, anyopne packaging the Python PIP version, please go ahead and
remove the current package.

Jari