Thomas Wouters wrote:
> On 5/8/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
>
>> test_ctypes
>> test test_ctypes failed -- Traceback (most recent call last):
>> File "/home/neal/python/trunk/Lib/ctypes/test/test_python_api.py", line
>> 41, in test_PyInt_Long
>> self.failUnlessEqual(grc(42), r
Raymond Hettinger wrote:
> Part of the mechanics also involves getting the users set-up on their
> own machines. For me, it was a complete PITA because of the
> Tortoise/Putty/Pageant/SSH2 dance and then trying to get Python to
> compile with the only compiler I had (MSVC++6). The advantage of a
Tim Peters wrote:
> [Martin v. Löwis]
>> I completely agree. Just make sure you master the mechanics of adding
>> committers.
>
> So there's a practical problem: is that procedure documented
> somewhere?
I once posted the procedure to all current pydotorg project admins.
I hesitate to post the p
[Raymond Hettinger]
> Part of the mechanics also involves getting the users set-up on their
> own machines.
Yes.
> For me, it was a complete PITA because of the
> Tortoise/Putty/Pageant/SSH2 dance and then trying to get Python to
> compile with the only compiler I had (MSVC++6). The advantage of
Tim Peters wrote:
>[Tim Peters, on giving commit privs to a sprinter after
> extracting a signed PSF contributor form]
>
>
>>>The more realistically ;-) I try to picture the suggested
>>>alternatives, the more sensible this one sounds. ...
>>>
>>>
>
>[Martin v. Löwis]
>
>
>>I completely
On 5/8/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
test_ctypestest test_ctypes failed -- Traceback (most recent call last): File "/home/neal/python/trunk/Lib/ctypes/test/test_python_api.py", line 41, in test_PyInt_Longself.failUnlessEqual(grc(42), ref42)
AssertionError: 336 != 337We've been se
On Sun, May 07, 2006, BJ?rn Lindqvist wrote:
>
> I do know enough about Python to know that the make_person function is
> a really bad example. The one obvious way to write make_peson is to
> use four positional arguments, name, age, phone, location and not
> complicate the function by throwing in
[Tim Peters, on giving commit privs to a sprinter after
extracting a signed PSF contributor form]
>> The more realistically ;-) I try to picture the suggested
>> alternatives, the more sensible this one sounds. ...
[Martin v. Löwis]
> I completely agree. Just make sure you master the mechanics of
I wrote:
> > - Variable field width specifiers use a nested version of the {}
> > syntax, allowing the width specifier to be either a positional
> > or keyword argument:
> >
> > "{0:{1}.{2}d}".format(a, b, c)
>
> This violates [the rule that '}' must be escaped]
Talin write
Michael Chermside mcherm.com> writes:
> One small comment:
>
> > The conversion specifier consists of a sequence of zero or more
> > characters, each of which can consist of any printable character
> > except for a non-escaped '}'.
>
> "Escaped"? How are they escaped? (with '\'?) If
One small comment:
> The conversion specifier consists of a sequence of zero or more
> characters, each of which can consist of any printable character
> except for a non-escaped '}'.
"Escaped"? How are they escaped? (with '\'?) If so, how are backslashes
escaped (with '\\'?) And does
On Fri, 28 Apr 2006, Thomas Heller wrote:
> I must work on the docs themselves, so I currently have only two things:
>
> - the table in the ctypes tutorial has a totally different look than the other
> tables in the docs. Compare
> http://docs.python.org/dev/lib/ctypes-simple-data-types.html
""Martin v. Löwis"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> - Paul Moore has contributed a Python build procedure for the
> free version of the 2003 compiler. This one is without IDE,
> but still, it should allow people without a VS 2003 license
> to work on Python itsel
Steven Bethard wrote:
> On 5/7/06, Edward Loper <[EMAIL PROTECTED]> wrote:
>> Talin wrote:
>>> Braces can be escaped using a backslash:
>>>
>>> "My name is {0} :-\{\}".format('Fred')
>>>
>>> Which would produce:
>>>
>>> "My name is Fred :-{}"
>> Do backslashes also need
Steven Bethard gmail.com> writes:
> I believe the proposal is taking advantage of the fact that '\{' is
> not interpreted as an escape sequence -- it is interpreted as a
> literal backslash followed by an open brace:
This is exactly correct.
-- Talin
__
Steven Bethard gmail.com> writes:
> I'm still not a big fan of mixing together getitem-style access and
> getattribute-style access. That makes classes that support both
> ambiguous in this context. You either need to specify the order in
> which these are checked (e.g. attribute then item or i
16 matches
Mail list logo
