Yingjie Lan wrote:
Seems you miss understood my notion of dynamic string.
Dynamic strings are expressions in disguise: the things
in between $...$ are plain old expressions (with optional
formatting specifications). They are evaluated
as if they were outside the dynamic string.
In that case
mwil...@the-wire.com wrote:
Yingjie Lan wrote:
Seems you miss understood my notion of dynamic string.
Dynamic strings are expressions in disguise: the things
in between $...$ are plain old expressions (with optional
formatting specifications). They are evaluated
as if they were outside the
rusi wrote:
Are there languages (other than python) in which single and double
quotes are equivalent?
Kernighan and Plauger's RATFOR (a pre-processor that added some C-like
syntax to FORTRAN) did that. Published in their book _Software Tools_.
Mel.
--
Roy Smith wrote:
In article jlmaid$hum$1...@dont-email.me, mwil...@the-wire.com wrote:
rusi wrote:
Are there languages (other than python) in which single and double
quotes are equivalent?
Kernighan and Plauger's RATFOR (a pre-processor that added some C-like
syntax to FORTRAN) did
Thomas Rachel wrote:
Am 07.04.2012 14:23 schrieb andrew cooke:
class IntVar(object):
def __init__(self, value=None):
if value is not None: value = int(value)
self.value = value
def setter(self):
def wrapper(stream_in, thunk):
Antti J Ylikoski wrote:
I wrote about a straightforward way to program D. E. Knuth in Python,
and received an excellent communcation about programming Deterministic
Finite Automata (Finite State Machines) in Python.
[ ... ]
#You can adjust that for your needs. Sometimes I have the states
Adam Skutt wrote:
[ ... ]
In the real world, if we were doing the math with pen and paper, we'd
stop as soon as we hit such an error. Equality is simply not defined
for the operations that can produce NaN, because we don't know to
perform those computations. So no, it doesn't conceptually
laymanzh...@gmail.com wrote:
I'm just learning Python. The python doc about mutable and hashable is
confusing to me.
In my understanding, there is no directly relation between mutable and
hashable in Python. Any class with __hash__ function is hashable.
According the wiki:
Ben Finney wrote:
[ ... ] Even worse is the
penchant for ‘foo .bar()’, the space obscures the fact that this is
attribute access.
I like the style sometimes when it helps to break the significantly different
parts out of
boilerplate:
libbnem. BN_add .argtypes = [ctypes.POINTER
On 4/30/2012 17:02, Kiuhnm wrote:
BignumTypePtr = ctypes.POINTER(BignumType)
for op, op_word in ((libbnem.BN_add, libbnem.BN_add_word),
(libbnem.BN_sub, libbnem.BN_sub_word)):
op.argtypes = [BignumTypePtr] * 3
op_word.argtypes = [BignumTypePtr, ctypes.c_ulong]
op.restype = op_word.restype
Kiuhnm wrote:
Regarding ctypes, try this to convince yourself that there's no problem
in reusing BignumPtrType:
from ctypes import POINTER, c_int
assert POINTER(c_int) is POINTER(c_int)
print ('POINTERs are shareable:', ctypes.POINTER (BignumType) is ctypes.POINTER
(BignumType))
[
Tim Chase wrote:
On 03/25/12 08:11, Chris Angelico wrote:
On Mon, Mar 26, 2012 at 12:03 AM, Tim Chase
python.l...@tim.thechases.com wrote:
Granted, this can be turned into an iterator with a yield, making the
issue somewhat moot:
No, just moving the issue to the iterator. Your iterator
Dennis Lee Bieber wrote:
On Sun, 25 Mar 2012 19:09:12 -0400, mwil...@the-wire.com declaimed the
following in gmane.comp.python.general:
Most of my database programs wind up having the boilerplate (not tested):
def rowsof (cursor):
names = [x[0] for x in cursor.description]
r =
13 matches
Mail list logo