@Wim
Where could I find the current state of the cling backend implementation?
Regards,
Dimitri.
PS. Please, ignore the email with the wrong subject.
> On Fri, Jan 10, 2014 at 12:00 PM, <pypy-dev-request(a)python.org> wrote:
>
>> Send pypy-dev mailing list submissions to
>> pypy-dev(a)python.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mail.python.org/mailman/listinfo/pypy-dev
>> or, via email,…
[View More] send a message with subject or body 'help' to
>> pypy-dev-request(a)python.org
>>
>> You can reach the person managing the list at
>> pypy-dev-owner(a)python.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of pypy-dev digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: cppyy and callbacks (Maciej Fijalkowski)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 10 Jan 2014 09:13:05 +0200
>> From: Maciej Fijalkowski <fijall(a)gmail.com>
>> To: Alex Stewart <foogod(a)gmail.com>
>> Cc: PyPy Developer Mailing List <pypy-dev(a)python.org>
>> Subject: Re: [pypy-dev] cppyy and callbacks
>> Message-ID:
>> <
>> CAK5idxQMp+phKVsazry6WqeqnoGSWPx5gaGL9wWrPz6fewTGBA(a)mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> On Fri, Jan 10, 2014 at 1:58 AM, Alex Stewart <foogod(a)gmail.com> wrote:
>> > I'd looked around a bit but could only find vague references to CINT,
>> and it
>> > wasn't even clear to me whether a full CINT backend really existed or
>> it was
>> > just a hack/experiment. Is it actually suitable for general-purpose
>> use?
>> >
>> > If so, I'd certainly be happy to try it.. how would one go about
>> switching
>> > to using the CINT backend instead of Reflex?
>> >
>> > --Alex
>>
>> Hey Alex.
>>
>> On a sidenote - can you please subscribe to pypy-dev so I don't have
>> to authorize every single one of your mail? It's relatively painless
>> and it's also very low traffic, so you won't get much uninteresting
>> stuff. Obviously feel free to unsubscribe once you're done.
>>
>> Cheers,
>> fijal
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> pypy-dev mailing list
>> pypy-dev(a)python.org
>> https://mail.python.org/mailman/listinfo/pypy-dev
>>
>>
>> ------------------------------
>>
>> End of pypy-dev Digest, Vol 33, Issue 6
>> ***************************************
>>
>
>
[View Less]
@Wim
Where could I find the current state of the cling backend implementation?
Regards,
Dimitri.
On Fri, Jan 10, 2014 at 12:00 PM, <pypy-dev-request(a)python.org> wrote:
> Send pypy-dev mailing list submissions to
> pypy-dev(a)python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/pypy-dev
> or, via email, send a message with subject or body 'help' to
> pypy-dev-request(a)python.…
[View More]org
>
> You can reach the person managing the list at
> pypy-dev-owner(a)python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pypy-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: cppyy and callbacks (Maciej Fijalkowski)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 10 Jan 2014 09:13:05 +0200
> From: Maciej Fijalkowski <fijall(a)gmail.com>
> To: Alex Stewart <foogod(a)gmail.com>
> Cc: PyPy Developer Mailing List <pypy-dev(a)python.org>
> Subject: Re: [pypy-dev] cppyy and callbacks
> Message-ID:
> <
> CAK5idxQMp+phKVsazry6WqeqnoGSWPx5gaGL9wWrPz6fewTGBA(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Fri, Jan 10, 2014 at 1:58 AM, Alex Stewart <foogod(a)gmail.com> wrote:
> > I'd looked around a bit but could only find vague references to CINT,
> and it
> > wasn't even clear to me whether a full CINT backend really existed or it
> was
> > just a hack/experiment. Is it actually suitable for general-purpose use?
> >
> > If so, I'd certainly be happy to try it.. how would one go about
> switching
> > to using the CINT backend instead of Reflex?
> >
> > --Alex
>
> Hey Alex.
>
> On a sidenote - can you please subscribe to pypy-dev so I don't have
> to authorize every single one of your mail? It's relatively painless
> and it's also very low traffic, so you won't get much uninteresting
> stuff. Obviously feel free to unsubscribe once you're done.
>
> Cheers,
> fijal
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev(a)python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>
>
> ------------------------------
>
> End of pypy-dev Digest, Vol 33, Issue 6
> ***************************************
>
[View Less]
Hey all,
There are a number of serious security improvements that have gone into the
stdlib SSL module in Python 3. For reasons that defy understanding, the
CPython maintainers have decided not to backport them to Python 2.
I'd like to backport a few of them, starting with: blocking SSLv2 by
default. How do people feel about this?
There are basically no servers on the internet that use SSLv2, as it's
completely broken, so all this does is prevent an attack. The downside is
that there'd be no …
[View More]way for a user to turn this off if we do it.
This would be a serious security hardening IMO.
(Note that this mostly only affects OS X, almost every other platform has
had SSLv2 turned off in OpenSSL itself).
Any objections?
Alex
--
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084
[View Less]
Hi all,
(sent for the pypy-dev mailing list)
A quick status update about STM. As I've said on IRC, I am *again*
looking at a new approach. This would change the core of STM, but
lets us keep most of the work we did on top of it, i.e. inside PyPy
and PyPy's JIT.
The pre-prototypes (called "c5" and "c6") as well as the current draft
(called "c7") tell me that it might work, and it might work very well
indeed, with a rather minor overhead. I cannot estimate the
percentages yet, but it's …
[View More]certainly much better than a 2x slow-down
--- more like 20%. The ideas apply better to low numbers of CPUs,
which is fine for the most common current-generation machines; it
would make using only two threads a big win already.
See README.txt for details here:
https://bitbucket.org/pypy/stmgc/raw/c7/c7 . Sorry if it's written in
a terse style. The basic limitation is that it can only work on
64-bit Linux.
If you're interested and by any chance you're near Neuchatel,
Switzerland, next Thursday 9th Jan, I'm sure Patrick and Pascal
wouldn't oppose you showing up at 11 at the University for this
presentation:
> """
> PyPy is a Python interpreter written in Python, best known for being
> often several times faster than the standard CPython. It is also a
> ground for experimenting with language implementation ideas (for
> Python and others). One such experiment uses STM to replace the
> global interpreter lock, in the now-well-published manner; plus some
> language design ideas about how to allow the end programmer to obtain
> longer, controlled transaction.
>
> I'll describe the current ideas for a very cheap STM design that
> focuses on this case: it is object-based, with an integrated GC;
> transaction lengths from medium to huge (several full GC cycles); no
> false conflicts; and focusing on low numbers of cpus for now. The
> current ideas seem to allow for a "read barrier" that is not a barrier
> at all, but only 2 to 4 cpu instructions that the machine can schedule
> in parallel, and that don't prevent regular compiler optimizations.
> (This relies on a Linux-only system call, though.) Additionally, this
> could potentially be extended with HyTM.
> """
A bientôt,
Armin.
[View Less]