On May 03, 2015, at 03:18 PM, Dmitry Shachnev wrote:
I have finally managed to finalize Sphinx 1.3 upload for experimental.
Thanks! I just added the Python 3.5 compatibility patch from upstream
github to sphinx's svn.
Also, if someone is interested in helping me to maintain Sphinx is Debian,
Hi Barry,
On Mon, 29 Jun 2015 11:23:36 -0400, Barry Warsaw wrote:
My Perl is pretty rusty, but I am happy to help out with Sphinx as time
allows.
Appreciated!
I just added a patch from upstream to support Python 3.5, which might
not help Debian right now, but is useful for my 3.5 rebuild
On Jun 29, 2015, at 08:06 PM, Dmitry Shachnev wrote:
Your packages were failing with 1.3.1-1, but are not failing with svn build
because I fixed the issue :)
Ah, I guess we need an ITP for snowballstemmer wink.
FWIW I have went through Yaroslav's logs and filed bugs for most of the
failing
Hi Sandro,
On Mon, 29 Jun 2015 13:12:33 -0400, Sandro Tosi wrote:
would you mind talking to the build reproducible folks to understand
how to make sphinx generating reproducible builds by default (instead
of patching all the software using it)?
Most of the issues are already fixed in 1.3
On Mon, Jun 29, 2015 at 2:41 PM, Dmitry Shachnev mity...@debian.org wrote:
Hi Sandro,
On Mon, 29 Jun 2015 14:08:40 -0400, Sandro Tosi wrote:
that's great news! I just recently (like end of last week) received a
patch for basemap to address dates in the doc, and it seemed like your
effort and
that's great news! I just recently (like end of last week) received a
patch for basemap to address dates in the doc, and it seemed like your
effort and their were not in sync. Might just be enough to give them a
heads up so they dont waste more time in fixing docs when a the new
release of sphinx
Hi Sandro,
On Mon, 29 Jun 2015 14:08:40 -0400, Sandro Tosi wrote:
that's great news! I just recently (like end of last week) received a
patch for basemap to address dates in the doc, and it seemed like your
effort and their were not in sync.
Looking at the patch in #790235, that is a
Dnia 2015-06-23, wto o godzinie 11:38 -0400, Barry Warsaw pisze:
[Apologies for the cross-posting! -BAW]
For Ubuntu 15.10 (Wily Werewolf), we want to make Python 3.5 the
default
Python 3 version. It's currently undecided whether we will keep
Python 3.4 as
a supported version, but a lot
On Jun 29, 2015, at 04:02 PM, Sandro Tosi wrote:
I dont have a patch for sphinx to fix that, but what I say is that
patching 59 packages to remove |today| instead of changing sphinx
/somehow/ is a waste of resources.
Maybe upstream would accept a patch similar to what I've done before. It
could
On Jun 29, 2015, at 11:43 PM, Tomasz Rybak wrote:
Sorry for maybe stupid question - but do I need to do anything
if PyOpenCL is on the list with green checkmark?
Generally, no, but if you can find any dependents of the package that are
FTBFS, then helping chase down the chain of problems would
On 06/30/2015 12:04 AM, Barry Warsaw wrote:
At the same time - are there plans to upload python3-defaults with enabled
support for Python 3.5?
Yes, but atm, there's no eta.
wrong. it's in experimental.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of
Hello.
Sorry for cross-posting, but topic touches two mailing lists.
There's new version of Boto, library to access AWS cloud services:
https://aws.amazon.com/blogs/aws/now-available-aws-sdk-for-python-3
-boto3/
It's API-incompatible with current Boto (2.38).
But both boto and boto3 can be
I dont have a patch for sphinx to fix that, but what I say is that
patching 59 packages to remove |today| instead of changing sphinx
/somehow/ is a waste of resources.
On Mon, Jun 29, 2015 at 3:26 PM, Dmitry Shachnev mity...@debian.org wrote:
Hi Sandro,
On Mon, 29 Jun 2015 15:11:00 -0400,
On Tue, Jun 30, 2015 at 4:14 AM, Barry Warsaw wrote:
Maybe upstream would accept a patch similar to what I've done before. It
could map |today| to the value of an environment variable, if it's set.
E.g. something like SPHINX_TODAY. Then pybuild, dh_python{2,3}, or some other
infrastructure
Hi Sandro,
On Mon, 29 Jun 2015 15:11:00 -0400, Sandro Tosi wrote:
well that requires to carry the patch in all the packages using
|today| instead of adapt sphinx to what Debian wants to achieve
(reproducible build) in the place that makes more sense: the tool
generating the doc. YMMV tho
On Mon, 29 Jun 2015 22:26:22 +0300, Dmitry Shachnev wrote:
According to codesearch, only 59 packages out of 608 using Sphinx have
|today| somewhere in their .rst files [1].
Forgotten reference:
[1] queries I used:
\|today\| path:.*\.rst# |today| in source files (not in
16 matches
Mail list logo
