similar to: [LLVMdev] lit support for Python3

> If anyone is interested in this support, I'd appreciate it if you changed > your setup to use Python3 for running the tests and let me know (or file > bugs) for any issues you find. Excellent! The only reason I set my interpreter back to 2.7 a while back was LLVM. Back to 3.2 now. Tim. P.S. All passes here too.

On Wed, Aug 14, 2013 at 1:15 PM, Tim Northover <t.p.northover at gmail.com>wrote: > > If anyone is interested in this support, I'd appreciate it if you changed > > your setup to use Python3 for running the tests and let me know (or file > > bugs) for any issues you find. > Great work, Daniel. All LLVM tests pass for me on trunk when running with Python 3.4 alpha.

On Wed, Aug 14, 2013 at 1:46 PM, Eli Bendersky <eliben at google.com> wrote: > > Now get rid of pre-2.6 Python support ;-) Not only it helps clean-up code, > by 2-and-3 coexistence is much easier. > > It looks like Daniel was able to add py3k support fairly cleanly. I'm not sure how much of a difference removing pre-2.6 support would make at this point. (also, let's

Hi, First of all - thanks very much to the team for the work that has gone into 4.10.0, I have downloaded it and am looking forward to upgrading :) I decided to try and use Python3 with my 4.10.0 upgrade, given the comments in the release notes; but I have some newbie questions that hopefully others can help with. I'm really not up to speed with python3 yet! This version of Debian evidently

On 24 February 2016 at 19:49, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Great! I'll circle around to this at some point. Despite the "obvious" > nature of it I still am wary of underestimating the cruftiness of the > buildbots, so I'll probably do it some time at night when the bots are > mostly green so that I can easily see if any bots

Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> writes: > On 24 February 2016 at 19:49, Sean Silva via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Great! I'll circle around to this at some point. Despite the "obvious" >> nature of it I still am wary of underestimating the cruftiness of the >> buildbots, so I'll probably do it some

https://bugzilla.netfilter.org/show_bug.cgi?id=1484 Bug ID: 1484 Summary: configure script fails to detect python3 Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at

> several people already asked what are the concrete benefits of breaking support for end-of-life python versions? Generally I think the only compelling argument is "for a given level of maintenance effort, you either sacrifice support for old-dead versions, or new versions", and obviously new versions should be preferred. The question is how much does it cost to interoperate. On

On Tue, Dec 17, 2019 at 12:55 PM Nico Weber <thakis at chromium.org> wrote: > On Tue, Dec 17, 2019 at 12:41 PM James Y Knight <jyknight at google.com> > wrote: > >> It sounds like you ran into a bug in the test infrastructure's code to >> determine if python3 is supported. Fixing that might be harder, but it only >> needs to be fixed once no matter how

On systems where python is still set to python2 the check will fail even though it is still completely possible to compile and use nbdkit. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- configure.ac | 2 +- plugins/python/nbdkit-python-plugin.pod | 13 +++++++------ 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/configure.ac

Hello Everyone, don't know how to fix this: [andy at localhost snappergui]$ sudo python3 ./__init__.py [sudo] password for andy: Traceback (most recent call last): File "./__init__.py", line 3, in <module> import gi ImportError: No module named 'gi' [andy at localhost snappergui]$ python ./__init__.py [andy at localhost snappergui]$ sudo python ./__init__.py

Hi all, Arch Linux (a rolling release distro) has updated to python3 a while back. python2 is still installed in parallel, but part of the ramifications of this move is the following:-0 1. /usr/bin/python points to /usr/bin/python3 instead of /usr/bin/python2 2. /usr/bin/python-config points to /usr/bin/python3-config instead of /usr/bin/python2-config I'm having problems with make for

> On 2016-Feb-24, at 12:48, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 24 February 2016 at 19:49, Sean Silva via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Great! I'll circle around to this at some point. Despite the "obvious" >> nature of it I still am wary of underestimating the cruftiness of the >>

Source: xen Version: 4.17.3+36-g54dacb5c02-1 Severity: important User: debian-python at lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes

Hallo, I?m using samba 4.11 from sernet and the vfs object full_audit. After update samba to 4.12 from sernet full_audit is broken and the shares with full_audit are not accessible. Can anyone tell me please how to install python 3 on centos7 while the Centos system needs python 2 but samba sould use python3? Thanks in advance, Peter

Looking for advice for best practices on fetching status of the samba server and share information. One option is to parse the output of `smbstatus` into a machine-readable format. But I noticed there are some apis documented. We are using samba 4.11 which is supposed to have full python3 api support. So the question is, can the share and lock information displayed in the `smbstatus` command

Hi List I want to install samba 4.10.2 on centos. but after run the ./configure command show "/usr/bin/env: python3: no such file or directory" how to fix this problem, my friends. tanks.

Great! I'll circle around to this at some point. Despite the "obvious" nature of it I still am wary of underestimating the cruftiness of the buildbots, so I'll probably do it some time at night when the bots are mostly green so that I can easily see if any bots *are* broken by this. -- Sean Silva On Tue, Feb 23, 2016 at 6:55 PM, Chris Matthews <chris.matthews at

It sounds like you ran into a bug in the test infrastructure's code to determine if python3 is supported. Fixing that might be harder, but it only needs to be fixed once no matter how much more python3 development there will be. Right now, most of our scripts were originally written for python 2, so certainly it's easy for them to support python 2. But, it was a lot of work by various

On Tue, Dec 4, 2012, at 03:23 AM, Sean Silva wrote: > > several people already asked what are the concrete benefits of breaking support for end-of-life python versions? > > Generally I think the only compelling argument is "for a given level > of maintenance effort, you either sacrifice support for old-dead > versions, or new versions", and obviously new versions