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
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
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
On Jun 25, 2015, at 04:57 PM, Dmitry Shachnev wrote:
>Sphinx needs python3-gi only for tests, so I think it will be easier to
>break the loop here. Search for "jstest" in debian/rules and comment that
>line out.
Thanks, it might indeed be easier this way. py3cairo is a mess. :/
Cheers,
-Barry
Hi Barry,
On Thu, 25 Jun 2015 09:38:49 -0400, Barry Warsaw wrote:
> It looks like we have a Build-Depends loop.
>
> python-sphinx (sphinx) -> python3-gi (pygobject) -> python3-cairo (py3cairo)
> -> python-sphinx
>
> All FTBFS in the PPA. I'm guessing this loop was introduced after the
> addition
It looks like we have a Build-Depends loop.
python-sphinx (sphinx) -> python3-gi (pygobject) -> python3-cairo (py3cairo)
-> python-sphinx
All FTBFS in the PPA. I'm guessing this loop was introduced after the
addition of Python 3.4, since it should affect every major Python version
transition.
I
On 06/24/2015 05:34 PM, Barry Warsaw wrote:
> On Jun 24, 2015, at 11:13 AM, Sandro Tosi wrote:
>
>> but it was the version from sid (1.8), not experimental (1.9)
>
> Ah, gotcha. I'll look at syncing 1.9 to the PPA.
>
> Cheers,
> -Barry
>
fwiw, numpy itself will fail with python 3.5 due to an
On Jun 24, 2015, at 11:13 AM, Sandro Tosi wrote:
>but it was the version from sid (1.8), not experimental (1.9)
Ah, gotcha. I'll look at syncing 1.9 to the PPA.
Cheers,
-Barry
pgpMlTmrrRzvg.pgp
Description: OpenPGP digital signature
On Jun 24, 2015, at 10:55 AM, Alastair McKinstry wrote:
>I'd recommend we build python3-numpy against Python 3.5 for experimental. Of
>my packages in the list that FTBFS, I think all of them fail on numpy (some
>on cython), while numpy builds fine against Python 3.5. We can test the
>transition i
but it was the version from sid (1.8), not experimental (1.9)
On Wed, Jun 24, 2015 at 11:05 AM, Barry Warsaw wrote:
> On Jun 24, 2015, at 10:55 AM, Alastair McKinstry wrote:
>
>>I'd recommend we build python3-numpy against Python 3.5 for experimental. Of
>>my packages in the list that FTBFS, I t
I'd recommend we build python3-numpy against Python 3.5 for experimental.
Of my packages in the list that FTBFS, I think all of them fail on numpy
(some on cython),
while numpy builds fine against Python 3.5. We can test the transition
in experimental.
regards
Alastair
On 23/06/2015 16:38, Barry
11 matches
Mail list logo
