From: Xavier Delaruelle <xavier.delaruelle@gmail.com>
To: Hamish MB <hamishmb@live.co.uk>
Cc: "marco.atzeri@gmail.com" <marco.atzeri@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Missing 'sphinx-build' command from python37-sphinx package
Date: Sun, 9 Aug 2020 10:38:29 +0200 [thread overview]
Message-ID: <CAExoBLsyh7OPUHBqCB9U9Oq6+xkLxQ8mA4Z5JMiwW8yczBjUTw@mail.gmail.com> (raw)
In-Reply-To: <DB7PR02MB3996B71344049C4A30D84BE3E7460@DB7PR02MB3996.eurprd02.prod.outlook.com>
If command names are versioned it is important to get a consistent way for
users to install THE package that provides the 'sphinx-build' command (the
one without version reference in the name). Without having to search which
specific package provides this command and without having to update this
package reference when a new minor version of Python is added.
Xavier
Le sam. 8 août 2020 à 22:08, Hamish MB via Cygwin <cygwin@cygwin.com> a
écrit :
> Perhaps versioned commands like sphinx-build36, 37, 38 and a sphinx-build
> command that defaults to 3.8?
>
> Hamish
> On 8 Aug 2020, at 20:07, Marco Atzeri via Cygwin <cygwin@cygwin.com
> <mailto:cygwin@cygwin.com>> wrote:
>
> On 08.08.2020 09:44, Xavier Delaruelle via Cygwin wrote:
> Hello,
>
> I am using cygwin through the AppVeyor CI environment to check my software
> build process and non-regression testsuite :
>
> https://ci.appveyor.com/project/xdelaruelle/modules
>
> In this environment I use python37-sphinx package to build the
> documentation of the software, which requires the 'sphinx-build' command.
>
> It seems that this 'sphinx-build' command has disappeared from
> python37-sphinx package recently:
>
>
> https://ci.appveyor.com/project/xdelaruelle/modules/builds/34537360/job/870u7prqtwgbwtnk
>
> Which is confirmed by listing package content:
>
>
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpython37-sphinx%2Fpython37-sphinx-3.1.2-1&grep=sphinx
>
> This issue is also affecting the python36-sphinx package.
>
> 36 was not changed from before, I will look for a way to provide a
> suitable sphinx-build that works with all 3.x versions
>
>
> python38-package contains the 'sphinx-build' command, however it seems
> there are some missing requirements to make this package operational. I
> get
> an "Could not import extension sphinx.builders<http://sphinx.builders>.epub3
> (exception: No module
> named 'sphinxcontrib')" error, see build log:
>
>
> https://ci.appveyor.com/project/xdelaruelle/modules/builds/34542552/job/9tw241syk4upr4r1
>
> Regards,
> Xavier
>
> noted.
> It is always difficult to establish which submodule are mandatory
> and which are just optional.
>
> It seems I nedd to deploy
>
> python38-sphinxcontrib-websupport
> python38-sqlalchemy
> python38-whoosh
>
> let me fews days
>
> Regards
> Marco
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
next prev parent reply other threads:[~2020-08-09 8:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 7:44 Xavier Delaruelle
2020-08-08 19:07 ` Marco Atzeri
2020-08-08 20:07 ` Hamish MB
2020-08-09 8:38 ` Xavier Delaruelle [this message]
2020-08-09 15:22 ` Marco Atzeri
2020-08-09 16:14 ` Xavier Delaruelle
2020-08-10 4:58 ` Xavier Delaruelle
2020-08-10 7:16 ` Marco Atzeri
2020-08-10 8:11 ` Marco Atzeri
2020-08-10 8:39 ` Xavier Delaruelle
2020-08-11 8:56 ` Xavier Delaruelle
2020-08-11 11:21 ` Marco Atzeri
2020-08-12 7:03 ` Marco Atzeri
2020-08-12 7:16 ` Xavier Delaruelle
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=CAExoBLsyh7OPUHBqCB9U9Oq6+xkLxQ8mA4Z5JMiwW8yczBjUTw@mail.gmail.com \
--to=xavier.delaruelle@gmail.com \
--cc=cygwin@cygwin.com \
--cc=hamishmb@live.co.uk \
--cc=marco.atzeri@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).