David Jones added the comment:
I believe the issue is only triggered if you actually have some suspicious
markup in your documentation (which is why your plain build on Sphinx 2 appears
to work).
Remove some lines from Doc/tools/susp-ignored.csv to trigger it.
--
nosy: +drj
David Jones added the comment:
The original bug report did not mention ls (note serhiy.storchaka). It is a red
herring.
I accept that the Python community doesn't care to have glob.glob sorted.
But then I think you should distance yourself from the shell in the
documentation.
It curr
New submission from David Jones:
This is probably related to #21913, but more specifically concerns the
documentation. I have a sub process of a larger program that handles a SIGTERM
sent by the main process for a clean shutdown. However, if I launch a parallel
task in the sub process, via
New submission from David Jones:
```
for f in glob.glob('input/*/*.dat'): print f
```
outputs:
```
input/ghcnm.v3.2.2.20140611/ghcnm.tavg.v3.2.2.20140611.qca.dat
input/ghcnm.v3.2.2.20140506/ghcnm.tavg.v3.2.2.20140506.qca.dat
```
Note that these are not in the right order. Compare
New submission from David Jones:
Consider the following code:
for z in zip([1]):pass
2to3 does not convert the zip in this code to list(zip(...)); it does not
change this code at all.
That can be an (obscure) bug because the zip in Python 2 has different
semantics from the zip in Python 3
David Jones added the comment:
Has there been any progress made on fixing this? I ran into this trying to
install numpy via pip, 32-bit python installation on 64-bit Centos 6.4. It
get's the compile flags right, but not the linker:
C compiler: gcc -pthread -fno-strict-aliasing -g -O2
David Jones added the comment:
I do realise that. I still think the mathematically correct answer should
be computed, since it can be.
--
___
Python tracker
<http://bugs.python.org/issue6
New submission from David Jones :
Consider: x//y != x//float(y) for some integer values of x and y.
For example, x = 2**54-1, and y = 2:
>>> x=2**54-1
>>> y=2
>>> x//y
9007199254740991L
>>> x//float(y)
9007199254740992.0
>>> _==x//y
False
I have
David Jones added the comment:
On 12 Feb 2009, at 09:00, David Jones wrote:
>
> David Jones added the comment:
>
> The following program does a very basic do-i-get-back-what-i-wrote
> test.
> sunau can't cope; I am investigating.
I see. sunau uses mu-law compression
David Jones added the comment:
The following program does a very basic do-i-get-back-what-i-wrote test.
sunau can't cope; I am investigating.
#!/usr/bin/env python
# $Id$
# Audio File Tests
import aifc
import sunau
import wave
import struct
import sys
from StringIO import StringIO
f
David Jones added the comment:
On 10 Feb 2009, at 21:15, David Jones wrote:
>
> David Jones added the comment:
>
> On 10 Feb 2009, at 16:57, Guilherme Polo wrote:
>
>>
>> Guilherme Polo added the comment:
>>
>> Now, is there some problem if we remove th
David Jones added the comment:
On 10 Feb 2009, at 16:57, Guilherme Polo wrote:
>
> Guilherme Polo added the comment:
>
> Now, is there some problem if we remove the calls to the "tell" method
> in _write_header ? See patch attached (tests ar
David Jones added the comment:
On 10 Feb 2009, at 13:02, David Jones wrote:
>
> I also note that my patch can be improved by removing its last 11
> lines.
Er, no it can't. What was I thinking?
___
Python tracker
<http://bugs.pyt
David Jones added the comment:
On 10 Feb 2009, at 12:28, Guilherme Polo wrote:
>
> Guilherme Polo added the comment:
>
> I'm really unsure about the proposed patch.
Perhaps my example was too trivial. The point is that if you call
setnframes then you can get wave.py to a
David Jones added the comment:
On 10 Feb 2009, at 12:28, Guilherme Polo wrote:
>
> Guilherme Polo added the comment:
>
> Wouldn't it be better if you only ignored the 'illegal seek' error
> instead of ignoring any ioerror (should it even be always discarded)
David Jones added the comment:
Attached is a patch which is a diff from this version of wave.py :
http://svn.python.org/view/*checkout*/python/trunk/Lib/wave.py?rev=54394
--
keywords: +patch
Added file: http://bugs.python.org/file13011/wave-20090210.patch
New submission from David Jones :
When using the wave module to output wave files, the output file cannot
be a Unix pipeline.
Example. The following program outputs a (trivial) wave file on stdout:
#!/usr/bin/env python
import sys
import wave
w = wave.open(sys.stdout, 'w')
w.setn
New submission from David Jones <[EMAIL PROTECTED]>:
Consider the web page:
http://www.python.org/doc/2.5.2/whatsnew/acks.html
(the problem appears throughout the whatsnew document, but that page
happens to be short and have more than one instance).
On my browser, Safari 3.1.2 on Inte
New submission from David Jones <[EMAIL PROTECTED]>:
After hacking the configure script to work around the issues
http://bugs.python.org/issue4025 and http://bugs.python.org/issue1633863
the build still fails:
building 'fcntl' extension
xlc_r -DNDEBUG -O -I. -I/home/u00
David Jones <[EMAIL PROTECTED]> added the comment:
This is still a problem for Python 2.6 on AIX 6.1.
The simplest fix is to change «CC=cc_r» to «CC=${CC:-xlc_r}» but I have no
idea how to go about changing the configure script.
--
nosy: +drj
versions: +Pyth
New submission from David Jones <[EMAIL PROTECTED]>:
Doing a plan "configure" then "make"; the compilation breaks due to //
style comments in a file called Objects/frameobject.c:
cc_r -qlanglvl=extc89 -c -DNDEBUG -O -I. -IInclude -I./Include -
DPy_BUILD_COR
David Jones <[EMAIL PROTECTED]> added the comment:
I agree, longs should be correctly rounded when coerced to floats.
There is an ugly (but amusing) workaround while people wait for this
patch: Go via a string:
int(float(repr(295147905179352891391)[:-1]))
Though I assume this relies
22 matches
Mail list logo
