David Abrahams wrote:
>>I would go a step further than Tim: Send me (*) a patch to msi.py (which
>>is used to build the distribution) that picks up the files and packages
>>them in the desired way, and I will include the files it outputs
>>in the official distribution. This is how the libpython24.a
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> David Abrahams wrote:
>>> Just to clarify - what we are asking for is library built with
>>> _DEBUG and no BOOST_DEBUG_PYTHON, that is the one compatible with
>>> default Python distribution.
>> I know you're trying to help, but I'm sure that's not
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> David Abrahams wrote:
>> Who knows what the whiny babies will accept? That said, I think
>> people would be happy with a .zip file containing whatever is built by
>> selecting the debug build in the VS project and asking it to build
>> everything. (
On 11/4/05, Eyal Lotem <[EMAIL PROTECTED]> wrote:
> I have a few claims, some unrelated, and some built on top of each
> other. I would like to hear your responses as to which are
> convincing, which arne't, and why. I think that if these claims are
> true, Python 3000 should change quite a bit.
>
David Abrahams wrote:
>>Just to clarify - what we are asking for is library built with _DEBUG
>>and no BOOST_DEBUG_PYTHON, that is the one compatible with default
>>Python distribution.
>
>
> I know you're trying to help, but I'm sure that's not making anything
> clearer for these people. The
I have a few claims, some unrelated, and some built on top of each
other. I would like to hear your responses as to which are
convincing, which arne't, and why. I think that if these claims are
true, Python 3000 should change quite a bit.
A. Metaclass code is black magic and few understand how it
David Abrahams wrote:
> Who knows what the whiny babies will accept? That said, I think
> people would be happy with a .zip file containing whatever is built by
> selecting the debug build in the VS project and asking it to build
> everything. (**)
I would go a step further than Tim: Send me (*)
Bronek Kozicki <[EMAIL PROTECTED]> writes:
> David Abrahams wrote:
>> Who knows what the whiny babies will accept? That said, I think
>> people would be happy with a .zip file containing whatever is built by
>> selecting the debug build in the VS project and asking it to build
>> everything. (**)
Tim Peters <[EMAIL PROTECTED]> writes:
> [David Abrahams]
>> For years, Boost.Python has been doing some hacks to work around the
>> fact that a Windows Python distro doesn't include the debug build of
>> the library.
>> ...
>> MS is recommending that we (Boost) start distributing a debug build of
Guido van Rossum <[EMAIL PROTECTED]> writes:
> I vaguely recall that there were problems with distributing the debug
> version of the MS runtime.
Right: the debug runtime dlls are not disributable.
> Anyway, why can't you do this yourself for all Boost users? It's all
> volunteer time, you know.
[David Abrahams]
> For years, Boost.Python has been doing some hacks to work around the
> fact that a Windows Python distro doesn't include the debug build of
> the library.
> ...
> MS is recommending that we (Boost) start distributing a debug build of the
> Python DLL with Boost, but Boost really
I vaguely recall that there were problems with distributing the debug
version of the MS runtime.
Anyway, why can't you do this yourself for all Boost users? It's all
volunteer time, you know...
--Guido
On 11/4/05, Charles Cazabon <[EMAIL PROTECTED]> wrote:
> David Abrahams <[EMAIL PROTECTED]> wr
David Abrahams <[EMAIL PROTECTED]> wrote:
>
> For years, Boost.Python has been doing some hacks to work around the fact
> that a Windows Python distro doesn't include the debug build of the library.
[...]
> Having to download the Python source and build the debug DLL was deemed
> unacceptable.
For years, Boost.Python has been doing some hacks to work around the
fact that a Windows Python distro doesn't include the debug build of
the library.
http://www.boost.org/libs/python/doc/building.html#variants
explains. We wanted to make it reasonably convenient for Windows
developers (and
[Guido van Rossum]
> Is there a way to prevent this kind of thing in the future, e.g. by
> removing or rejecting change log messages with characters that are
> considered invalid in XML?
Suppose TOP is the top of the Subversion repository. The easiest way is
providing a TOP/hook/pre-commit scri
M.-A. Lemburg wrote:
> Fredrik Lundh wrote:
>
>>the runtime warning you get when you use non-ascii characters in
>>python source code points the poor user to this page:
>>
>>http://www.python.org/peps/pep-0263.html
>>
>>which tells the user to add a
>>
>># -*- coding: -*-
>>
>>to the sour
On 11/3/05, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > 3. If someone does want to associate values with objects, he can
> > explicitly use id:
> > dct[id(x)] = 3.
>
> This is fragile. Once all references to x are dropped,
> it is possible for another object to be created having
> the same id that x
Fredrik Lundh wrote:
> the runtime warning you get when you use non-ascii characters in
> python source code points the poor user to this page:
>
> http://www.python.org/peps/pep-0263.html
>
> which tells the user to add a
>
> # -*- coding: -*-
>
> to the source, and then provides a mo
the runtime warning you get when you use non-ascii characters in
python source code points the poor user to this page:
http://www.python.org/peps/pep-0263.html
which tells the user to add a
# -*- coding: -*-
to the source, and then provides a more detailed syntax description
as a RE pa
19 matches
Mail list logo
