Darrin Thompson schrieb:
> On 5/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> p &sqlite3InitCallback
>>
>
> (gdb) p $sqlite3InitCallback
> $1 = void
Please try '&' instead of '$'. It's the address of that function
I was after (to then find out whether it is in the address range
of the ex
On 5/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> p &sqlite3InitCallback
>
(gdb) p $sqlite3InitCallback
$1 = void
g.
> Try "info shared" in gdb. Not sure whether that works on OSX,
> though.
>
Worked beautifully!
The smoking gun: something is hauling in the system provided sqlite3
> One feature that is easily addable and will certainly make installing
> python on vista nicer, is to add authenticode signing to the install.
This I question very much. I experimented with authenticode before 2.4,
and found it an unacceptable experience. When the MSI file starts
running, install
Just to chime in from the IronPython side (better late than never I suppose):
If we need to get access to the frame which is calling super then we can make
that happen in IronPython. It just means that super gets treated like we treat
eval today and won't work if it's been aliased.
-Origin
Hi,
I uploaded couple of patches to fix bugs.
1) http://www.python.org/sf/1720897 to fix the bug 668596 (distutils
chops the first character of filenames).
2) http://www.python.org/sf/1713041 to fix the bug 1712742 (pprint
handles depth argument incorrectly).
Both the patches are extremely smal
On 5/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> The question for python-dev is "how can I debug that further, and where
> should I submit a patch" :-)
>
I have no problem with that. :-)
> > (gdb) info threads
> > * 1 process 18968 local thread 0x1003 0x900e41d1 in strtol_l ()
> > (gdb
On 5/28/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Brett Cannon schrieb:
> Unfortunately the pre-commit hook
> does not specify what line a change was made on so I have no clue where
> it is failing (maybe this should be added?).
It creates a reindent.Reindenter on the new contents, then
On 5/29/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> What happens when you use the binary installer at python.org? This is
> build with a newer version of sqlite as well (because the installer
> supports OSX 10.3).
>
Hmmm. I hadn't thought of checking the sqlite version in there. I did
use the
At 1:14 PM + 5/29/07, Kristján Valur Jónsson wrote:
>> -Original Message-
>>
>> Microsoft's command line cannot cope with two pathnames that must be
>> quoted, so if the command path itself must be quoted, then no argument
>> to
>> the command can be quoted. There are tricky hacks that
On 26 May, 2007, at 6:45, Darrin Thompson wrote:
First of all 1000 apologies if this is the wrong list. Please redirect
me if necessary.
I'm attempting to build python 2.5.1 fat binaries on OSX and
statically link to a newer sqlite than what ships with OSX. (3.3.17).
I'm getting "Bus Error" e
> -Original Message-
> From: "Martin v. Löwis" [mailto:[EMAIL PROTECTED]
> > Just imagine the a school teacher who in good faith wants to
> introduce
> > his pupils to the wonderful programming language of Python, but
> > when he installs it, all kinds of scary looking warnings drive him
>
Martin v. Löwis wrote:
>> I have a set of extensions that use SWIG to wrap my own C++ library.
>> This library, on a day-to-day basis is built against VS8 since the rest
>> of our product suite is. Right now I have no way to work with this code
>> using VS8 since the standard distribution is buil
> -Original Message-
>
> Microsoft's command line cannot cope with two pathnames that must be
> quoted, so if the command path itself must be quoted, then no argument
> to
> the command can be quoted. There are tricky hacks that can work around
> this mind-boggling stupidity, but life is
From a user's POV, I'm +1 on having overloadable boolean functions. In many
cases I had to resort to overload add or neg instead of and & not, I foresee
a lot of cases where the and overload could be used to join objects which
represent constraints. Overloadable boolean operators could also be us
I recommend that those people install the official binaries. Why do
you
need to build the binaries from source, if all you want is to build
extensions?
I've been following this discussion and it seems like an appropriate
place to mention such a scenario which I have encountered myself and
Martin v. Löwis schrieb:
>> As I said before, you don't really need that when you can (and should!) just
>> run
>> reindent.py over the source file yourself, not care about any diffs and just
>> resubmit.
>
> Right. So I withdraw my offer to do anything about the hook.
I think printing something
> As I said before, you don't really need that when you can (and should!) just
> run
> reindent.py over the source file yourself, not care about any diffs and just
> resubmit.
Right. So I withdraw my offer to do anything about the hook.
Regards,
Martin
___
Scott Dial schrieb:
> Martin v. Löwis wrote:
>> Brett Cannon schrieb:
>>> Unfortunately the pre-commit hook
>>> does not specify what line a change was made on so I have no clue where
>>> it is failing (maybe this should be added?).
>>
>> It creates a reindent.Reindenter on the new contents, then
Martin v. Löwis wrote:
> Brett Cannon schrieb:
>> Unfortunately the pre-commit hook
>> does not specify what line a change was made on so I have no clue where
>> it is failing (maybe this should be added?).
>
> It creates a reindent.Reindenter on the new contents, then invokes
> .run() on it, and
Georg Brandl schrieb:
> Martin v. Löwis schrieb:
>>> Odd... the call worked here (SVN 1.4.3). Which version is the server using?
>> 1.1. Subversion did a grand renaming at some point. I fixed most of the
>> functions when deploying the script, but apparently missed some.
>
> Okay. Is an upgrade pl
20 matches
Mail list logo
