On Sun, Jan 27, 2013 at 3:42 PM, abhishek goswami
wrote:
> Hi,
> I am working in Python-C ApI (Integrated Project). The Project has migrated
> to 64 bit machine from 32 bit machine. Every thing was working fine in 32
> bit machine.
> But we getting following error in 64 bit machine.
> " Python int
Hi,
I am working in Python-C ApI (Integrated Project). The Project has migrated to
64 bit machine from 32 bit machine. Every thing was working fine in 32 bit
machine.
But we getting following error in 64 bit machine.
" Python int too large to convert to C long".
When I start debug the code and
On Sun, Jan 27, 2013 at 2:21 PM, ezio.melotti
wrote:
> http://hg.python.org/cpython/rev/07488c3c85f1
> changeset: 81772:07488c3c85f1
> branch: 3.3
> parent: 81770:a0756411c527
> user:Ezio Melotti
> date:Sun Jan 27 06:20:14 2013 +0200
> summary:
> Fix a few typos and
On Sun, Jan 27, 2013 at 3:25 AM, Ezio Melotti wrote:
> Hi,
> I'm not sure these changes are an improvement.
>
> On Fri, Jan 25, 2013 at 8:49 PM, brett.cannon
> wrote:
>> http://hg.python.org/cpython/rev/792810303239
>> changeset: 81735:792810303239
>> user:Brett Cannon
>> date:
On Sat, Jan 26, 2013 at 8:48 PM, Cameron Simpson wrote:
> On 25Jan2013 21:07, Nick Coghlan wrote:
> | It's a configurable setting in the same way that -Q makes the
> | behaviour of "/" configurable in Python 2 (so your hypothetical
> | example isn't hypothetical at all - it's a description the -Q
On 25Jan2013 21:07, Nick Coghlan wrote:
| It's a configurable setting in the same way that -Q makes the
| behaviour of "/" configurable in Python 2 (so your hypothetical
| example isn't hypothetical at all - it's a description the -Q option),
| and -R makes random hashing configurable in 2.7 and 3
On 25Jan2013 12:24, Victor Stinner wrote:
| 2013/1/25 Charles-François Natali :
| > You can actually count me in the cloexec=False camp, and against the
| > idea of a configurable default value.
|
| Oh ok.
I'm leaning to this view myself also.
| > Why the default value shouldn't be tunable:
| >
On Sat, 26 Jan 2013 17:19:32 +0100, Antoine Pitrou wrote:
> On Sat, 26 Jan 2013 17:03:59 +0100
> Stefan Krah wrote:
> > Stefan Krah wrote:
> > > I'm not sure how accurate the output is for measuring these things, but
> > > according to ``ls'' and ``du'' the option is indeed quite worthless:
> >
On Sat, 26 Jan 2013 17:03:59 +0100
Stefan Krah wrote:
> Stefan Krah wrote:
> > I'm not sure how accurate the output is for measuring these things, but
> > according to ``ls'' and ``du'' the option is indeed quite worthless:
> >
> > ./configure CFLAGS="-Os -s" LDFLAGS="-s" && make
> > 1.8M Jan
Stefan Krah wrote:
> I'm not sure how accurate the output is for measuring these things, but
> according to ``ls'' and ``du'' the option is indeed quite worthless:
>
> ./configure CFLAGS="-Os -s" LDFLAGS="-s" && make
> 1.8M Jan 26 16:36 python
> ./configure --without-doc-strings CFLAGS="-Os -s"
Antoine Pitrou wrote:
> Well... Speaking personally, I'd much rather stop shipping and
> "supporting" such obscure build options. I'd like to hear about people
> using production Pythons --without-doc-strings.
I'm not sure how accurate the output is for measuring these things, but
according to ``
On Sun, 27 Jan 2013 01:07:14 +1000
Nick Coghlan wrote:
> On Sun, Jan 27, 2013 at 12:45 AM, Antoine Pitrou wrote:
> >
> > Hello,
> >
> > On Sat, 26 Jan 2013 11:55:12 +0100
> > Stefan Krah wrote:
> >>
> >> I've subverted the build master authority on the FreeBSD-9.0 bot by
> >> exporting with_doc_
On Sun, Jan 27, 2013 at 12:45 AM, Antoine Pitrou wrote:
>
> Hello,
>
> On Sat, 26 Jan 2013 11:55:12 +0100
> Stefan Krah wrote:
>>
>> I've subverted the build master authority on the FreeBSD-9.0 bot by
>> exporting with_doc_strings=no. This is to test #16143 and #10156.
>
> Well... Speaking person
Hello,
On Sat, 26 Jan 2013 11:55:12 +0100
Stefan Krah wrote:
>
> I've subverted the build master authority on the FreeBSD-9.0 bot by
> exporting with_doc_strings=no. This is to test #16143 and #10156.
Well... Speaking personally, I'd much rather stop shipping and
"supporting" such obscure buil
On 26.01.13 12:55, Stefan Krah wrote:
Some tests assume that docstrings are present, so there will be a couple
of failures. If someone wants to work on easy issues, this is your chance.
http://bugs.python.org/issue17040
___
Python-Dev mailing list
P
> So, if we agree that "cloexec-by-default" is a desirable goal, despite
> the inconsistency with POSIX (just as changing integer division was
> seen as desirable, despite the inconsistency with C) ...
I don't plan to enable cloexec by default in a near future, nor in python
4. Someone else may ch
Hi,
I've subverted the build master authority on the FreeBSD-9.0 bot by
exporting with_doc_strings=no. This is to test #16143 and #10156.
Some tests assume that docstrings are present, so there will be a couple
of failures. If someone wants to work on easy issues, this is your chance.
If the f
17 matches
Mail list logo
