Am 16.01.2012 17:28, schrieb Antoine Pitrou:
> On Mon, 16 Jan 2012 11:17:42 -0500
> Brett Cannon wrote:
>> Is the change to the pyc format big enough news to go into the release PEP?
>> Or should that just be a "What's New" topic?
>
> "What's New" sounds enough to me. The change doesn't enable an
> From: python-dev-bounces+jaraco=jaraco@python.org [mailto:python-
> dev-bounces+jaraco=jaraco@python.org] On Behalf Of Jason R. Coombs
> Sent: Monday, 16 January, 2012 19:01
>
> I'm unsure if the conversion from 9 to 10 or 10 to 9 can be as simple as
the
> vs9to8 suggests. When I run the
On Mon, Jan 16, 2012 at 4:16 PM, Victor Stinner <
victor.stin...@haypocalc.com> wrote:
> 2012/1/17 Tim Delaney :
> > What if in a pathological collision (e.g. > 1000 collisions), we
> increased
> > the size of a dict by a small but random amount?
>
> It doesn't change anything, you will still get
2012/1/17 Tim Delaney :
> What if in a pathological collision (e.g. > 1000 collisions), we increased
> the size of a dict by a small but random amount?
It doesn't change anything, you will still get collisions.
Victor
___
Python-Dev mailing list
Python-
On Mon, Jan 16, 2012 at 18:01, Jason R. Coombs
> My goal in adding the upgrade code was to provide a one-step upgrade for
> developers with only VS 10 installed. That's what vs-upgrade in
> jaraco.develop does.
Upgrading to 2010 requires some code changes in addition to the
conversion, so the proc
> From: "Martin v. Löwis" [mailto:mar...@v.loewis.de]
> Sent: Monday, 16 January, 2012 16:25
>
> I'd be hesitant to put too many specialized tools into the tree that will
> become unmaintained. Please take a look at the vs9to8 tool in PCbuild; if
you
> could adjust that to support VS 10, it would b
On 17 January 2012 10:14, Tim Delaney wrote:
> On 17 January 2012 09:23, Paul McMillan wrote:
>
>> This is why the "simply throw an error" solution isn't a complete fix.
>> Making portions of an interface unusable for regular users is clearly
>> a bad thing, and is clearly applicable to other ty
On 17 January 2012 09:23, Paul McMillan wrote:
> This is why the "simply throw an error" solution isn't a complete fix.
> Making portions of an interface unusable for regular users is clearly
> a bad thing, and is clearly applicable to other types of poisoned data
> as well. We need to detect col
> As I understand it, the way the attack works is that a *single*
> malicious request from the attacker can DoS the server by eating CPU
> resources while evaluating a massive collision chain induced in a dict
> by attacker supplied data. Explicitly truncating the collision chain
> boots them out a
> If there are no objections, I’ll work to extract the aforementioned
> functionality from the jaraco.develop modules and into a portable script
> and put together a proof-of-concept in the default branch. The build
> script should not interfere with any build bots or other existing build
> process
> From: Brian Curtin [mailto:br...@python.org]
> Sent: Monday, 16 January, 2012 15:20
>
> 2010 is adequate for limited use but the test suite doesn't pass, so I
would be
> hesitant to add support and/or documentation for building with it until we
> actually support it the same as or in place of 200
On Mon, Jan 16, 2012 at 14:00, Jason R. Coombs wrote:
> The second thing I notice is the scripts assume Visual Studio 2008. And
> while I recognize that Python is specifically built against Visual Studio
> 2008 for the official releases and that Visual Studio 2008 may be the only
> officially-supp
On Sun, Jan 15, 2012 at 9:44 AM, Guido van Rossum wrote:
> On Sun, Jan 15, 2012 at 8:46 AM, Stefan Behnel wrote:
>
>> Guido van Rossum, 15.01.2012 17:10:
>> > On Sun, Jan 15, 2012 at 6:30 AM, Stefan Behnel wrote:
>> >> Terry Reedy, 14.01.2012 06:43:
>> >>> On 1/13/2012 8:58 PM, Gregory P. Smith w
The current scripts for building Python lack some things to be desired.
The first thing I notice when I try to build Python on Windows is the
scripts expect to be run inside of a Visual Studio environment, the
environment of which is only defined inside of a cmd.exe context. This means
the scri
On Mon, 16 Jan 2012 11:17:42 -0500
Brett Cannon wrote:
> Is the change to the pyc format big enough news to go into the release PEP?
> Or should that just be a "What's New" topic?
"What's New" sounds enough to me. The change doesn't enable any new
feature, it just makes an issue much less likely
Is the change to the pyc format big enough news to go into the release PEP?
Or should that just be a "What's New" topic?
On Fri, Jan 13, 2012 at 15:18, georg.brandl wrote:
> http://hg.python.org/peps/rev/ea3ffa3611e5
> changeset: 4012:ea3ffa3611e5
> user:Georg Brandl
> date:Fri
Hi,
Le 14/01/2012 15:31, Sandro Tosi a écrit :
On Sat, Jan 14, 2012 at 04:24, Éric Araujo wrote:
Doc/glossary.rst:520: WARNING: unknown keyword: nonlocal
That’s a mistake I did in cefe4f38fa0e. This sentence should be
removed.
Do you mean revert this whole hunk:
[...]
or just "The :keyword:
python wrote:
jbk
[snip 560+ lines of quoted text]
Please delete irrelevant text when replying to digests, and replace the
subject line with a meaningful subject.
--
Steven
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/
jbk
python-dev-requ...@python.org编写:
>Send Python-Dev mailing list submissions to
> python-dev@python.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.python.org/mailman/listinfo/python-dev
>or, via email, send a message with subject or body 'help' to
>
Am 07.01.2012 18:57, schrieb "Martin v. Löwis":
I just tried porting Python as a Metro (Windows 8) App, and failed.
Metro Apps use a variant of the Windows API called WinRT that still
allows to write native applications in C++, but restricts various APIs
to a subset of the full Win32 functionali
20 matches
Mail list logo