Displaying 15 results from an estimated 15 matches for "szorc".
2014 Jun 26
4
[LLVMdev] Python version requirement for LLVM
On Wed, Jun 25, 2014 at 5:52 PM, Gregory Szorc <gregory.szorc at gmail.com>
wrote:
> As much as I like killing support for Python 2.6 and below, RHEL is
> usually the blocker. They still have 2.4 under support. Only the RHEL that
> was released a few weeks ago finally has 2.7.
>
Given the amount of complexity required to bui...
2012 Mar 16
3
[LLVMdev] Python bindings in tree
..."time to market" and get more eyes and early testers
using the bindings. From my experience with Clang, people aren't exactly
lining up to review Python patches, so I fear that new Python features
would be sitting in patch purgatory instead of being tested by early
adopters.
Gregory Szorc
gregory.szorc at gmail.com
2012 Mar 16
0
[LLVMdev] Python bindings in tree
Hello,
Am Donnerstag, 15. März 2012, 21:15:02 schrieb Gregory Szorc:
> There was some talk on IRC last week about desire for Python bindings to
> LLVM's Object.h C interface. So, I coded up some and you can now find
> some Python bindings in trunk at bindings/python. Currently, the
> interfaces for Object.h and Disassembler.h are implemented.
FYI:...
2012 Dec 01
2
[LLVMdev] Minimum Python Version
On Sat, Dec 1, 2012 at 2:08 PM, Dimitry Andric <dimitry at andric.com> wrote:
> On 2012-12-01 21:57, Gregory Szorc wrote:
>>
>> I'd like to continue the discussion about minimum Python versions from the
>> "Use multiprocessing instead of threading" thread in its own thread because
>> I feel it warrants additional discussion.
>
> ...
>
>> For these reasons, I...
2012 Dec 01
0
[LLVMdev] Minimum Python Version
On 2012-12-01 21:57, Gregory Szorc wrote:
> I'd like to continue the discussion about minimum Python versions from the "Use multiprocessing instead of threading" thread in its own thread because I feel it warrants additional discussion.
...
> For these reasons, I urge LLVM to drop support for Python older than 2....
2012 Dec 01
11
[LLVMdev] Minimum Python Version
I'd like to continue the discussion about minimum Python versions from the
"Use multiprocessing instead of threading" thread in its own thread because
I feel it warrants additional discussion.
In that thread, we were discussing maintaining support for Python 2.4 and
2.5. The latest response is:
On Fri, Nov 30, 2012 at 1:40 PM, Daniel Dunbar <daniel at zuster.org> wrote:
>
2012 Dec 01
0
[LLVMdev] Minimum Python Version
On Sat, Dec 1, 2012 at 2:14 PM, Eli Bendersky <eliben at google.com> wrote:
> On Sat, Dec 1, 2012 at 2:08 PM, Dimitry Andric <dimitry at andric.com> wrote:
> > On 2012-12-01 21:57, Gregory Szorc wrote:
> >>
> >> I'd like to continue the discussion about minimum Python versions from
> the
> >> "Use multiprocessing instead of threading" thread in its own thread
> because
> >> I feel it warrants additional discussion.
> >
> >...
2014 Jun 26
4
[LLVMdev] Python version requirement for LLVM
http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as a
minimum required version. I'd like to use argparse
<https://docs.python.org/dev/library/argparse.html> in a script and be able
to test this script. This requires Python 2.7. This version has been around
since 2010, and afaiu, is available on all modern platforms. Is there any
reason not to change minimum required
2012 Dec 03
1
[LLVMdev] Minimum Python Version
...ter I accidentally submitted a patch which used post Python-2.4 features that people pointed out broke stuff.)
Regards,
Dave
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Dimitry Andric
Sent: 01 December 2012 22:08
To: Gregory Szorc
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Minimum Python Version
On 2012-12-01 21:57, Gregory Szorc wrote:
> I'd like to continue the discussion about minimum Python versions from the "Use multiprocessing instead of threading" thread in its own thread because I feel it war...
2012 Mar 19
2
[LLVMdev] Python bindings in tree
On Sun, Mar 18, 2012 at 09:52:12PM -0700, Gregory Szorc wrote:
> The automatic generation of the Python ctypes interfaces using the Clang
> Python bindings is pretty friggin cool!
A nice side effect is that everything is added to the interface. So it
is easy to add a small proxy over the lib that shows which parts of
the llvm-c API that is exerci...
2012 Mar 17
3
[LLVMdev] Python bindings in tree
At Fri, 16 Mar 2012 14:12:08 +0100,
Christoph Grenz wrote:
>
> Hello,
>
> Am Donnerstag, 15. März 2012, 21:15:02 schrieb Gregory Szorc:
> > There was some talk on IRC last week about desire for Python bindings to
> > LLVM's Object.h C interface. So, I coded up some and you can now find
> > some Python bindings in trunk at bindings/python. Currently, the
> > interfaces for Object.h and Disassembler.h are...
2012 Dec 07
0
[LLVMdev] Minimum Python Version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/1/12 12:57 PM, Gregory Szorc wrote:
>
> I believe LLVM should drop support for Python 2.4 and 2.5 for 2 main
reasons:
>
> 1) Python 2.4 and 2.5 are end-of-lifed
> 2) Python 3 is coming
Entering the discussion a bit late, but I'd like to make a plug here for
using Cython for any official Python bindings. The...
2012 Mar 21
0
[LLVMdev] Python bindings in tree
On Mon, Mar 19, 2012 at 10:44 AM, Anders Waldenborg <anders at 0x63.nu> wrote:
>
> * Auto generated vs manual ctypes declarations.
>
This is purely a cosmetic difference, as we both take the same approach of
registering functions on a global/shared ctypes library instance. I think
automatic is the way to go (just as long as the automatically generated
code is easy to diff when
2012 Dec 03
0
[LLVMdev] Minimum Python Version
...7.0 now on its 4th beta and soon to be release candidate
status).
I personally run Sid/Unstable in order to get general release builds of
LLVM/Clang > 2.9, never mind 3.2.
It seems reasonable to target 2.7.3 as the oldest python release.
- Marc J. Driftmeyer
On 12/01/2012 12:57 PM, Gregory Szorc wrote:
> I'd like to continue the discussion about minimum Python versions from
> the "Use multiprocessing instead of threading" thread in its own
> thread because I feel it warrants additional discussion.
>
> In that thread, we were discussing maintaining support for...
2012 Mar 19
0
[LLVMdev] Python bindings in tree
On 3/17/2012 4:14 PM, Anders Waldenborg wrote:
> FYI:
>
> I've also been working on new python bindings.
>
> My bindings are written using ctypes (just like the in-tree
> clang/cindex bindings). Most of Core.h is bound, and stuff from
> ExecutionEngine.h, Analysis, BitReader, BitWriter. The have fairly
> good test coverage (using nosetests). The ctypes definitions are