Guido van Rossum wrote:
>
> Index: Objects/funcobject.c
> ===
> --- Objects/funcobject.c(revision 59154)
> +++ Objects/funcobject.c(working copy)
> @@ -643,8 +643,10 @@
> static PyObject *
> func_descr_get(PyObject *
On Fri, Nov 23, 2007 at 10:32:25PM -0600, [EMAIL PROTECTED] wrote:
->
-> Brett> Looks like Skip's r59137 fix for working with tracing has led to
-> Brett> test_doctest to be broken on 2.5 and the trunk (at least
-> Brett> according to the buildbots). Can someone either revert the
->
On Nov 22, 2007 11:12 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > It looks like we're in agreement to drop unbound methods and have a
> > reasonable set or arguments around it (e.g. keep staticmethod, no
> > changes to methods of builtin types, etc.). Do we need a
Facundo Batista wrote:
> Mark Dickinson found out that a lot of time was lost internally in
> decimal.py when dealing with the Decimal mantissas.
>
> He changed the way that mantissa was stored, from a tuple of ints, to
> a plain string (each character a digit). This achieved a speedup of
> around
Brett> Looks like Skip's r59137 fix for working with tracing has led to
Brett> test_doctest to be broken on 2.5 and the trunk (at least
Brett> according to the buildbots). Can someone either revert the
Brett> commit or fix it? I would normally do it myself but US
Brett> Thank
> It looks like we're in agreement to drop unbound methods
+1 It is a bit cleaner to simply return the unmodified function.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
Martin v. Löwis wrote:
> I think struct compiling should carry the file name, starting in
> PyAST_FromNode.
Thanks! I was trying to add the filename to node but it required too
many changes. I really wonder why I wasn't touching the compiling struct.
Christian
___
> Should the node structure gain an additional field to drag the filename
> around? Or can we simply life with the fact that the user won't get a
> filename in the deprecation warning?
I think struct compiling should carry the file name, starting in
PyAST_FromNode.
Regards,
Martin
___
Looks like Skip's r59137 fix for working with tracing has led to
test_doctest to be broken on 2.5 and the trunk (at least according to
the buildbots). Can someone either revert the commit or fix it? I
would normally do it myself but US Thanksgiving has me tied up to not
do too much beyond bitchin
Christian Heimes wrote:
> Should the node structure gain an additional field to drag the filename
> around?
Why not?
Early on in the design of the Pyrex compiler, I made the decision
that every parse tree node would contain a source filename and
position, down to character resolution. It's paid o
> VS 2008 Express doesn't have a devenv command
Can you please try out whether the buildbot commands have
any chance to work with the Express edition?
Buildbot operators will have to install VS 2008 one way
or the other, and it would be nice if you could provide
instructions for them what precise
Phillip J. Eby wrote:
> class MoneyField(Field):
> # does need staticmethod because two_decimal_places
> # doesn't take a self
> converter = staticmethod(two_decimal_places)
Okay, I see what you mean now. But you could just as well wrap
it in a function that takes self and discards it
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> bsddb is automatically build by a build step. But you have to convert
> the project files in build_win32 to VS 2008 first. Simply open the
> solution file and let VS convert the projects.
VS 2008 Express doesn't have a devenv command, so
On 23/11/2007, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2007-11-23 18:40, Christian Heimes wrote:
> > M.-A. Lemburg wrote:
> >> Why not include the prebuilt libraries of all external libs in SVN
> >> as well ?
> >
> > For one I'm still using Beta 2 of the standard edition and I'm not
> > allow
Hi there,
since ssl module is still in development I thought it would have been
better asking such question here instead of on comp.lang.python.
I'm interested in using the ssl module with asyncore but since there's
no real documentation about it yet I've been not able to write
something useful wit
Hi there,
since ssl module is still in development I thought it would have been
better asking such question here instead of on comp.lang.python.
I'm interested in using the ssl module with asyncore but since there's
no real documentation about it yet I've been not able to write
something useful wit
On Nov 23, 2007 10:02 AM, Andreas Raab <[EMAIL PROTECTED]> wrote:
> Nick Coghlan wrote:
> > Issues with collocating the compiled files with the source files do
> > arise occasionally, but they can generally be resolved by having root
> > run compileall [1] over the affected directories. In cases wh
Hi people!
Two news. A big speed up, and now we reached some stable state.
Mark Dickinson found out that a lot of time was lost internally in
decimal.py when dealing with the Decimal mantissas.
He changed the way that mantissa was stored, from a tuple of ints, to
a plain string (each character
ACTIVITY SUMMARY (11/16/07 - 11/23/07)
Tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
1321 open (+20) / 11654 closed (+20) / 12975 total (+40)
Open issues with patches: 413
Average durati
Nick Coghlan wrote:
> Issues with collocating the compiled files with the source files do
> arise occasionally, but they can generally be resolved by having root
> run compileall [1] over the affected directories. In cases where users
> are able to modify source files (hence leading to the need
Christian Heimes wrote:
> M.-A. Lemburg wrote:
>> Why not include the prebuilt libraries of all external libs in SVN
>> as well ?
>
> For one I'm still using Beta 2 of the standard edition and I'm not
> allowed to distribute binaries build with the Beta. With the new
> pre-build steps it's also ve
On 2007-11-23 18:40, Christian Heimes wrote:
> M.-A. Lemburg wrote:
>> Why not include the prebuilt libraries of all external libs in SVN
>> as well ?
>
> For one I'm still using Beta 2 of the standard edition and I'm not
> allowed to distribute binaries build with the Beta. With the new
> pre-bui
M.-A. Lemburg wrote:
> Why not include the prebuilt libraries of all external libs in SVN
> as well ?
For one I'm still using Beta 2 of the standard edition and I'm not
allowed to distribute binaries build with the Beta. With the new
pre-build steps it's also very easy to build the dependencies. I
Nick> As I recall, the PEP was withdrawn because Skip didn't have the
Nick> time and/or level of interest needed to champion it any more, and
Nick> nobody else was interested in taking on the task.
Correct. I only implemented what I did because it seemed like an
interesting concept
Facundo Batista schrieb:
> 2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
>
>> Well, I'm exaggerating a bit but you probably get my point. The core
>> developers can't keep up with new bugs and check old bugs at the same
>> time. The resources are already stretched thin. But Brett gave me an
>
2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
> Well, I'm exaggerating a bit but you probably get my point. The core
> developers can't keep up with new bugs and check old bugs at the same
> time. The resources are already stretched thin. But Brett gave me an
One *fantastic* tool that exists
On 2007-11-23 16:59, Christian Heimes wrote:
> Paul Moore wrote:
>> _ssl
>>
>>
>> Christian has been making changes to allow this to build without Perl,
>> so I gave it a try. I used openssl 0.9.8g, which I extracted to the
>> build directory (I noticed afterwards that this is the same version
Andreas Raab wrote:
> While googling this issue, I noticed that the status of PEP 304 says
> "withdrawn" but since most of the discussion around it seems to be a
> couple of years old, I thought I'd ask if anyone has done something in
> this area recently. If not, a pointer to the place which ma
Facundo Batista schrieb:
>> won't need developer access to the svn. Instead their task is cleaning
>> up the tracker, categorizing bugs and checking patches. The tracker sure
>> contains a lot of outdated junk and already fixed bugs.
>
> One way to do this is to create a monthly (or each two mont
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Why are you building the projects step by step? "Build solution" or F6
> builds everything in the right order.
Because I'm clueless :-)
I knew there must be a way of building the lot, but couldn't find it -
I haven't used Visual Studio
Paul Moore wrote:
> On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
>> I really like to throw out the old junk to have a clean script. Maybe I
>> could leave the old msvccompiler alone and put the new code into
>> distutils.msvc9compiler?
>
> That might work. I'm not sure if throwing th
Paul Moore wrote:
> Install Visual C++ 2008 Express Edition. Only select Silverlight from
> the options (no documentation or SQL Server - Silverlight probably
> isn't actually needed either).
> I already had the Platform SDK installed, but did nothing to tell VS
> about it, or to integrate it. I do
On 23/11/2007, Tim Golden <[EMAIL PROTECTED]> wrote:
> For practicality's sake I'd very much like to help get this
> to the point where you can build Python *and* extensions with
> the VS Express compilers (including, critically, the pywin32
> stuff).
Pywin32 needs MFC (and at one stage, ATL, alth
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> I've a preliminary patch for distutils.msvccompiler at
> http://bugs.python.org/issue1455. I haven't applied the patch because
> it's not backward compatible with VC 7 and VS 6. We haven't yet agreed
> how to address backward compatibilit
2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
> The Python bug tracker contains more than 1,300 bugs and it's growing.
> And growing ... and growing. I'm picking a bug once in a while or
> tossing some invalid bugs away but it's a helpless cause. The bugs are
> augmenting with anybody stopping
Tim Golden wrote:
> Ah. Thanks for that last bit. I thought this might not build
> without the full VS, so I didn't try poking round for a
> nasm-alike.
I've changed the build_ssl.py script to build openssl for nasm instead
of ml/masm. The MS assembler for x86 is only available in the standard
and
Andreas Raab schrieb:
> Hi -
>
> I'm having a few problems with our (embedded) Python interpreter trying
> to write .pyc files in the installation of our product (which actually
> sometimes works and sometimes doesn't depending on OS and paranoia level
> involved). This can give raise to a few
Paul Moore wrote:
> I have just built the current trunk version of Python on Windows,
> using the new PCBuild9 directory, and Visual Studio 2008 Express
> Edition.
>
> Everything went extremely well. I include below my notes on what I
> did, for reference. To be honest, there's nothing in here tha
Christian Heimes schrieb:
> Dear fellow Python developers!
>
> The Python bug tracker contains more than 1,300 bugs and it's growing.
Not speaking of the 432 bugs that weren't migrated from SourceForge
(though I don't know how many of them were open).
> And growing ... and growing. I'm picking a
Hi -
I'm having a few problems with our (embedded) Python interpreter trying
to write .pyc files in the installation of our product (which actually
sometimes works and sometimes doesn't depending on OS and paranoia level
involved). This can give raise to a few very confusing situations and
I'd
I have just built the current trunk version of Python on Windows,
using the new PCBuild9 directory, and Visual Studio 2008 Express
Edition.
Everything went extremely well. I include below my notes on what I
did, for reference. To be honest, there's nothing in here that really
warrants a change to
Christian Heimes schrieb:
> Hello!
>
> I'm having a bit of a trouble getting the deprecation warning for
> backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c
> nor the node structures have access to the filename.
On a related note, every time you start a Python interpreter w
Dear fellow Python developers!
The Python bug tracker contains more than 1,300 bugs and it's growing.
And growing ... and growing. I'm picking a bug once in a while or
tossing some invalid bugs away but it's a helpless cause. The bugs are
augmenting with anybody stopping them.
Well, I'm exaggerat
Hello!
I'm having a bit of a trouble getting the deprecation warning for
backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c
nor the node structures have access to the filename.
Should the node structure gain an additional field to drag the filename
around? Or can we simply l
At 07:57 PM 11/23/2007 +1300, Greg Ewing wrote:
>Phillip J. Eby wrote:
>>If you are configuring it per-class and accessing it per-instance,
>>and reusing an existing function, you have to make it a staticmethod.
>
>I don't understand that. Can you provide an example?
def two_decimal_places(text)
At 08:19 PM 11/22/2007 -0800, Guido van Rossum wrote:
>It looks like we're in agreement to drop unbound methods and have a
>reasonable set or arguments around it (e.g. keep staticmethod, no
>changes to methods of builtin types, etc.). Do we need a PEP? It's
>essentially a 2-line change in funcobjec
46 matches
Mail list logo
