On Fri, Apr 8, 2011 at 3:29 AM, Jesse Noller wrote:
> On Thu, Apr 7, 2011 at 7:52 PM, Michael Foord
> wrote:
>> On 08/04/2011 00:36, Anthony Scopatz wrote:
>>
>> On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord
>> wrote:
>>>
>>> On 07/04/2011 22:41, Antoine Pitrou wrote:
On Thu, 07 Apr 2
> I've found that abstractmethod and similar decorators "don't work" in
> classes, inherited from built-in types other than object.
http://bugs.python.org/issue5996
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
On Thu, Apr 7, 2011 at 8:29 PM, Jesse Noller wrote:
> On Thu, Apr 7, 2011 at 7:52 PM, Michael Foord
> wrote:
> > On 08/04/2011 00:36, Anthony Scopatz wrote:
> >
> > On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord >
> > wrote:
> >>
> >> On 07/04/2011 22:41, Antoine Pitrou wrote:
> >>>
> >>> On Thu
Hello,
I've found that abstractmethod and similar decorators "don't work" in
classes, inherited from built-in types other than object.
For example:
>>> import abc
>>> class MyBase(metaclass=abc.ABCMeta):
@abc.abstractmethod
def foo(): pass
>>> MyBase()
Traceback (most recent call
On Thu, Apr 7, 2011 at 7:52 PM, Michael Foord wrote:
> On 08/04/2011 00:36, Anthony Scopatz wrote:
>
> On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord
> wrote:
>>
>> On 07/04/2011 22:41, Antoine Pitrou wrote:
>>>
>>> On Thu, 07 Apr 2011 17:32:24 -0400
>>> Tres Seaver wrote:
>
> Right now,
On Fri, Apr 8, 2011 at 8:12 AM, Michael Foord wrote:
> On 07/04/2011 20:18, Robert Collins wrote:
>>
>> On Fri, Apr 8, 2011 at 4:49 AM, Michael Foord
>> wrote:
>>>
>>> You mean that the test run keeps the test instances alive for the whole
>>> test
>>> run so instance attributes are also kept ali
> Because tracker is ugly.
Is this an unbiased opinion? :)
Eugene
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive
On 12:07 am, jans...@parc.com wrote:
exar...@twistedmatrix.com wrote:
On 08:31 pm, jans...@parc.com wrote:
>My Intel Snow Leopard 2 build slave has gone into outer-space again.
>
>When I look at it, I see buildslave taking up most of a CPU (80%),
and
>nothing much else going on. The twistd lo
On Thu, Apr 7, 2011 at 6:52 PM, Michael Foord wrote:
>
>
*some* good benchmarks in place (and the pypy ones are good ones).
>
Agreed. The PyPy ones are good.
>
> So I'm still with Jesse on this one. If there is any "discussion phase" as
> part of the Gsoc project it should be very strictly boun
exar...@twistedmatrix.com wrote:
> On 08:31 pm, jans...@parc.com wrote:
> >My Intel Snow Leopard 2 build slave has gone into outer-space again.
> >
> >When I look at it, I see buildslave taking up most of a CPU (80%), and
> >nothing much else going on. The twistd log says:
> >
> >[... much omitte
On 08/04/2011 00:36, Anthony Scopatz wrote:
On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord
mailto:fuzzy...@voidspace.org.uk>> wrote:
On 07/04/2011 22:41, Antoine Pitrou wrote:
On Thu, 07 Apr 2011 17:32:24 -0400
Tres Seavermailto:tsea...@palladion.com>> wrote:
On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord wrote:
> On 07/04/2011 22:41, Antoine Pitrou wrote:
>
>> On Thu, 07 Apr 2011 17:32:24 -0400
>> Tres Seaver wrote:
>>
>>> Right now, we are talking about building "speed.python.org" to test
the speed of python interpreters, over time, and alongsid
On 08:31 pm, jans...@parc.com wrote:
My Intel Snow Leopard 2 build slave has gone into outer-space again.
When I look at it, I see buildslave taking up most of a CPU (80%), and
nothing much else going on. The twistd log says:
[... much omitted ...]
2011-04-04 08:35:47-0700 [-] sending app-leve
On 07/04/2011 22:41, Antoine Pitrou wrote:
On Thu, 07 Apr 2011 17:32:24 -0400
Tres Seaver wrote:
Right now, we are talking about building "speed.python.org" to test
the speed of python interpreters, over time, and alongside one another
- cython *is not* an interpreter.
Cython is out of scope f
In article <4d9e2054.3080...@voidspace.org.uk>,
Michael Foord wrote:
> On 07/04/2011 21:31, Bill Janssen wrote:
> > My Intel Snow Leopard 2 build slave has gone into outer-space again.
> > [snip...]
> > So it's been spinning its wheels for 3 days.
> >
> > Sure looks like the connection attempt is
On Tue, Apr 5, 2011 at 6:37 AM, Nick Coghlan wrote:
> 1. Making "docstring" an attribute of the Function node rather than
> leaving it embedded as the first statement in the suite (this avoids
> issues where AST-based constant folding could potentially corrupt the
> docstring)
> 2. Collapsing Num,
Michael Foord wrote:
> On 07/04/2011 21:31, Bill Janssen wrote:
> > My Intel Snow Leopard 2 build slave has gone into outer-space again.
> > [snip...]
> > So it's been spinning its wheels for 3 days.
> >
> > Sure looks like the connection attempt is failing, for some reason.
> >
> > I'm using the
2011/4/7 Maciej Fijalkowski :
>> AFAIK the AST is
>> CPython-specific so should be treated with the same attitude as
>> changes to the bytecode. That means, do it conservatively, since there
>> *are* people who like to write tools that manipulate or analyze this,
>> and while they know they're doin
On Thu, 07 Apr 2011 17:32:24 -0400
Tres Seaver wrote:
> >
> > Right now, we are talking about building "speed.python.org" to test
> > the speed of python interpreters, over time, and alongside one another
> > - cython *is not* an interpreter.
> >
> > Cython is out of scope for this.
>
> Why is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/07/2011 04:28 PM, Jesse Noller wrote:
> On Thu, Apr 7, 2011 at 3:54 PM, Anthony Scopatz wrote:
>> Hi Daniel,
>> Thanks for putting this together. I am a huge supporter of benchmarking
>> efforts. My brief comment is below.
>>
>> On Wed, Apr 6,
On 07/04/2011 21:31, Bill Janssen wrote:
My Intel Snow Leopard 2 build slave has gone into outer-space again.
[snip...]
So it's been spinning its wheels for 3 days.
Sure looks like the connection attempt is failing, for some reason.
I'm using the stock Twisted that comes with Snow Leopard -- tr
On 06/04/2011 17:52, DasIch wrote:
Hello Guys,
I would like to present my proposal for the Google Summer of Code,
concerning the idea of porting the benchmarks to Python 3.x for
speed.pypy.org. I think I have successfully integrated the feedback I
got from prior discussions on the topic and I wou
My Intel Snow Leopard 2 build slave has gone into outer-space again.
When I look at it, I see buildslave taking up most of a CPU (80%), and
nothing much else going on. The twistd log says:
[... much omitted ...]
2011-04-04 08:35:47-0700 [-] sending app-level keepalive
2011-04-04 08:45:47-0700 [-
On Thu, Apr 7, 2011 at 3:54 PM, Anthony Scopatz wrote:
> Hi Daniel,
> Thanks for putting this together. I am a huge supporter of benchmarking
> efforts. My brief comment is below.
>
> On Wed, Apr 6, 2011 at 11:52 AM, DasIch wrote:
>>
>> 1. Definition of the benchmark suite. This will entail con
On 07/04/2011 20:18, Robert Collins wrote:
On Fri, Apr 8, 2011 at 4:49 AM, Michael Foord wrote:
You mean that the test run keeps the test instances alive for the whole test
run so instance attributes are also kept alive. How would you solve this -
by having calling a TestSuite (which is how a t
Hi Daniel,
Thanks for putting this together. I am a huge supporter of benchmarking
efforts. My brief comment is below.
On Wed, Apr 6, 2011 at 11:52 AM, DasIch wrote:
>
> 1. Definition of the benchmark suite. This will entail contacting
> developers of Python implementations (CPython, PyPy, Ir
> AFAIK the AST is
> CPython-specific so should be treated with the same attitude as
> changes to the bytecode. That means, do it conservatively, since there
> *are* people who like to write tools that manipulate or analyze this,
> and while they know they're doing something CPython and
> version-s
On Fri, Apr 8, 2011 at 4:49 AM, Michael Foord wrote:
> You mean that the test run keeps the test instances alive for the whole test
> run so instance attributes are also kept alive. How would you solve this -
> by having calling a TestSuite (which is how a test run is executed) remove
> members fr
On Thu, Apr 7, 2011 at 12:57 PM, Raymond Hettinger
wrote:
..
> * provide a clean way to post code snippets
> (we've had past issues with whitespace being gobbled-up)
>
What would really help is if someone would figure out how to stop the
tracker from removing the lines that start with the python
On Apr 7, 2011, at 9:22 AM, anatoly techtonik wrote:
> On Thu, Apr 7, 2011 at 7:01 AM, Benjamin Peterson wrote:
>> 2011/4/6 anatoly techtonik :
>>> Is it a good idea to have code highlighting in tracker?
+0
That has its highpoints;
* give tracker entries a more professional appearance
close
On Thu, Apr 7, 2011 at 11:22, anatoly techtonik wrote:
> On Thu, Apr 7, 2011 at 7:01 AM, Benjamin Peterson
> wrote:
> > 2011/4/6 anatoly techtonik :
> >> Is it a good idea to have code highlighting in tracker?
> >
> > Why would we need it?
>
> Because tracker is ugly.
It's a bug tracker, not a
On 07/04/2011 17:18, Fabio Zadrozny wrote:
I actually created a bug entry for this
(http://bugs.python.org/issue11798) and just later it occurred that I
should've asked in the list first :)
So, here's the text for opinions:
Right now, when doing a test case, one must clear all the variables
cre
> On Thu, Apr 7, 2011 at 7:01 AM, Benjamin Peterson
> wrote:
>> 2011/4/6 anatoly techtonik :
>>> Is it a good idea to have code highlighting in tracker?
>>
>> Why would we need it?
>
> Because tracker is ugly.
That's not a good enough reason. I'm -1 on adding this: it's yet another
thing to maint
2011/4/7 anatoly techtonik :
> On Thu, Apr 7, 2011 at 7:01 AM, Benjamin Peterson wrote:
>> 2011/4/6 anatoly techtonik :
>>> Is it a good idea to have code highlighting in tracker?
>>
>> Why would we need it?
>
> Because tracker is ugly.
So we should add some highlighted code to spice it up? :)
On Thu, Apr 7, 2011 at 7:01 AM, Benjamin Peterson wrote:
> 2011/4/6 anatoly techtonik :
>> Is it a good idea to have code highlighting in tracker?
>
> Why would we need it?
Because tracker is ugly.
___
Python-Dev mailing list
Python-Dev@python.org
http:
On Thu, Apr 7, 2011 at 12:40 AM, Antoine Pitrou wrote:
>
> For the record, I've tried to make the force build form clearer on the
> buildbot Web UI. See e.g.:
> http://www.python.org/dev/buildbot/all/builders/x86%20OpenIndiana%20custom
Cool. I've recently discovered buildbot page for twisted. It
I actually created a bug entry for this
(http://bugs.python.org/issue11798) and just later it occurred that I
should've asked in the list first :)
So, here's the text for opinions:
Right now, when doing a test case, one must clear all the variables
created in the test class, and I believe this sh
On Wed, Apr 06, 2011 at 11:04:08AM +0200, John Arbash Meinel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> ...
> > #. ``__version_info__`` SHOULD be of the format returned by PEP 386's
> >``parse_version()`` function.
>
> The only reference to parse_version in PEP 386 I coul
On 07/04/2011 12:59, Nick Coghlan wrote:
On Thu, Apr 7, 2011 at 9:10 PM, Michael Foord wrote:
I really dislike this way of specifying the version. For a start it is
really ugly.
More importantly it means the version information is *only* available if the
package has been installed by "packagin
On Thu, Apr 7, 2011 at 9:10 PM, Michael Foord wrote:
> I really dislike this way of specifying the version. For a start it is
> really ugly.
>
> More importantly it means the version information is *only* available if the
> package has been installed by "packaging", and so isn't available for the
On Thu, 07 Apr 2011 12:10:59 +0100
Michael Foord wrote:
> On 06/04/2011 15:26, Nick Coghlan wrote:
> > On Wed, Apr 6, 2011 at 6:22 AM, Glenn Linderman
> > wrote:
> >> With more standardization of versions, should the version module be
> >> promoted
> >> to stdlib directly?
> > When Tarek lands
On 07/04/2011 12:10, Michael Foord wrote:
On 06/04/2011 15:26, Nick Coghlan wrote:
On Wed, Apr 6, 2011 at 6:22 AM, Glenn
Linderman wrote:
With more standardization of versions, should the version module be
promoted
to stdlib directly?
When Tarek lands "packaging" (i.e. what distutils2 become
On 06/04/2011 15:26, Nick Coghlan wrote:
On Wed, Apr 6, 2011 at 6:22 AM, Glenn Linderman wrote:
With more standardization of versions, should the version module be promoted
to stdlib directly?
When Tarek lands "packaging" (i.e. what distutils2 becomes in the
Python 3.3 stdlib), the standardise
On Thu, Apr 7, 2011 at 5:05 PM, Glenn Linderman wrote:
> On 4/6/2011 11:53 PM, Nick Coghlan wrote:
> They all use distutils (or setuptools or distutils2) though, which is
> what packaging replaces.
>
> (Sorry for not making that clear - it's easy to forget which aspects
> of these issues aren't co
On 4/6/2011 11:53 PM, Nick Coghlan wrote:
On Thu, Apr 7, 2011 at 2:55 PM, Glenn Linderman wrote:
__version__ = "7.9.7" # replaced by "packaging"
If you don't upload your module to PyPI, then you can do whatever you
want with your versioning info. If you *do* upload it to PyPI, then
part of
On Thu, Apr 7, 2011 at 3:15 PM, Stefan Behnel wrote:
> Assuming there always is an "equivalent" Python implementation anyway, what
> about using that as a fallback for input types that the C implementation
> cannot deal with?
>
> Or would it be a larger surprise for users if the code ran slower wh
46 matches
Mail list logo
