Perhaps related to the discussion of denial-of-service vulnerabilities is the
matter of controlling access to remote resources. I suppose that after the
following bug was closed, no improvements were made to the standard library:
http://bugs.python.org/issue2124
Do Python programs still visit t
Stefan Behnel wrote:
>
> This is off-topic for this list, but the main problem with PyPy is that
> you'll quickly hit a lot of walls when you try to use it for anything
> serious in the area. It's true that there is a certain level of
> interoperability with CPython extensions, but calling it a "fo
Travis Oliphant wrote:
>
> With Numba and Blaze we have been doing a lot of work on what essentially
> is compiler technology and realizing more and more that we are treading on
> ground that has been plowed before with many other projects. So, we
> wanted to create a web-site and perhaps even a
Robert Whitney wrote:
> To Whoever this may concern,
>
> I believe the exploit in use on the Python Wiki could have been the
> following remote arbitrary code execution exploit that myself and some
> fellow researchers have been working with over the past few days. I'm
> not sure if this has
On Saturday 03 November 2012 12:29:57 anatoly techtonik wrote:
> I don't have access to modify the front page.
> http://wiki.python.org/moin/FrontPage
Yes, access was restricted a while ago because of spamming.
> To me it lacks one more section concerning help with core development
> infrastructu
Stefan Behnel wrote:
> anatoly techtonik, 05.07.2012 21:41:
> >
> > Make the bloody FAQ and summarize this stuff? Why waste each others
> > time?
>
> Yes, that is exactly the question.
>
> It takes time to write things up nicely. I mean, once someone has pointed
> out to you that this has been disc
Stefan Behnel wrote:
> Paul Boddie, 01.07.2012 02:22:
> > Is there any reason why the compiler-sig mailing list wasn't chosen as a
> > venue
>
> Even I didn't know that this list even existed. And looking at the archives
> now, it's hard to see any relevant
Edward K. Ream wrote:
> Hello all,
>
> GvR has asked me to announce the python-static-type-checking google
> group http://groups.google.com/group/python-static-type-checking to
> python-dev.
>
> Consider it announced. Anyone from python-dev who likes may become a
> member.
Is there any reason why
bruce bushby wrote:
>
> My main concern was that a freshly compiled Python attempts to open 168
> non-existent files before starting.
This has been a longstanding problem with CPython and, despite assertions to
the contrary, a significant factor on some embedded systems.
> I understand that an i
Skip wrote:
> Antoine wrote:
> > 94 changesets? If you want to avoid risking conflicts, you should "hg
> > pull" and "hg up" (or "hg pull -u") before you start working on
> > something (just like you "svn up"'ed before working on something).
>
> Sorry, this workflow is still new and hugely confusin
Hello,
I've been following this thread all week at work, but I thought it might be
time to respond to the different remarks in a single response, given that I
am involved in editing and maintaining the Wiki on python.org, and I had a
strong enough opinion about such things to give a talk about
On Monday 08 December 2008 22:54:41 Guido van Rossum wrote:
>
> From my experience with SQL, it's nearly as bad as Python in that
> every single one of the 200+ reserved words in a typical
> implementation cannot be used as a name in any context without using
> double quotes.
SQL is a big language
On Sat Dec 6 21:29:09 CET 2008, Guido van Rossum wrote:
>
> On Sat, Dec 6, 2008 at 11:38 AM, Warren DeLano
> wrote:
> > As someone somewhat knowledgable of how parsers work, I do not
> > understand why a method/attribute name "object_name.as(...)" must
> > necessarily conflict with a standalone ke
13 matches
Mail list logo
