On Aug 5, 2011 12:29 AM, "Greg Stein" wrote:
>
>
> On Aug 4, 2011 5:33 PM, "Hyrum K Wright"
wrote:
> >...
>
> > I think we've been operating under a 2.4 assumption for dev builds,
> > but other bits have slowly crept in. I would not be opposed to
> > bumping the dev requirement to 2.6, as most d
On Aug 4, 2011 5:33 PM, "Hyrum K Wright" wrote:
>...
> I think we've been operating under a 2.4 assumption for dev builds,
> but other bits have slowly crept in. I would not be opposed to
> bumping the dev requirement to 2.6, as most distros seem to be running
> at least that these days.
I'm on
On Wed, Aug 3, 2011 at 2:28 PM, Peter Samuelson wrote:
>
>> On Wed, Aug 3, 2011 at 3:03 PM, Peter Samuelson wrote:
>> > Further checking: the new exception syntax is new to Python 2.6.
>> > Given that this script is only used in dev builds (not from
>> > tarballs), someone remind me: what's our P
> On Wed, Aug 3, 2011 at 3:03 PM, Peter Samuelson wrote:
> > Further checking: the new exception syntax is new to Python 2.6.
> > Given that this script is only used in dev builds (not from
> > tarballs), someone remind me: what's our Py version requirement for
> > dev builds? It is not specifie
On Wed, Aug 3, 2011 at 3:03 PM, Peter Samuelson wrote:
>
> [Douglas Mencken]
> > # fix (wrong in year 2011) python2-specific syntax
> > sed -i 's/IOError, e/IOError as e/' ./build/getversion.py
>
> To clarify: Doug wanted this so he could build using Python 3. I've
> explained that we don't supp
[Douglas Mencken]
> # fix (wrong in year 2011) python2-specific syntax
> sed -i 's/IOError, e/IOError as e/' ./build/getversion.py
To clarify: Doug wanted this so he could build using Python 3. I've
explained that we don't support Python 3 in the bindings, so it doesn't
really make sense to use
# fix (wrong in year 2011) python2-specific syntax
sed -i 's/IOError, e/IOError as e/' ./build/getversion.py
7 matches
Mail list logo
