Changes by James Tocknell :
--
nosy: +aragilar
___
Python tracker
<http://bugs.python.org/issue18391>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from James Luscher:
Doc for 3.4: at 6.1.3.1. Format Specification Mini-Language
indicates that:
"The precision is a decimal number indicating how many digits should be
displayed after the decimal point for a floating point value"
Yet I find that I get this behavio
James Domingo added the comment:
Per SilentGhost's request, reposting my message from issue 27890 here --
The platform.release() function in Python 3.5.1 returns the correct value on
Windows 2008 Server R2:
C:\Users\jdoe\Documents\Python>python-3.5.1-embed-amd64\python.exe
Pyth
New submission from Eddie James:
JSON does not correctly encode dbus.Double types, even though all other dbus
types are handled fine. I end up with output like this (0.25 is the floating
point value): dbus.Double(0.25, variant_level=1)
Found that the encoding uses repr() for float objects but
Changes by Eddie James :
Added file: http://bugs.python.org/file44334/json-float-str-2.7.patch
___
Python tracker
<http://bugs.python.org/issue27934>
___
___
Python-bug
Eddie James added the comment:
Understood on 2.7, I wasn't aware it would cause any issues.
Dbus.Double is not a subclass of float unfortunately. Problem is that all Dbus
types seem to have a custom tp_repr method that returns that strange formatting
I mentioned. So repr won't be t
Eddie James added the comment:
Thanks Mark, yes you installed the right package.
OK I didn't dig deep enough in the sub class. And yea, there shouldn't be any
difference between float.__repr__ and float.__str__. Obviously repr calls the
object's tp_repr method, while float.__r
Eddie James added the comment:
Wait what about the json C code for 2.7? That's still using PyObject_Repr()
which will call tp_repr for dbus.Double... Any suggestions?
--
___
Python tracker
<http://bugs.python.org/is
Eddie James added the comment:
Python 2.7 also already behaves correctly for other dbus types:
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import
Changes by Eddie James :
Added file: http://bugs.python.org/file44349/json-float-repr-2.7.patch
___
Python tracker
<http://bugs.python.org/issue27934>
___
___
Python-bug
Changes by James Lu :
--
nosy: +James Lu
___
Python tracker
<http://bugs.python.org/issue28326>
___
___
Python-bugs-list mailing list
Unsubscribe:
James Schneider added the comment:
Please consider for implementation in 3.6. I'd love it even more for 3.5 but I
don't think that will happen. With the latest patch, I don't believe there are
any backwards-incompatible
Changes by James Lu :
--
nosy: +James Lu
___
Python tracker
<http://bugs.python.org/issue28663>
___
___
Python-bugs-list mailing list
Unsubscribe:
James C. McPherson added the comment:
While using LD_LIBRARY_PATH might be ok for a quick run by hand,
it's preferable to use an RPATH when linking for more long term
usages.
--
nosy: +jmcp
___
Python tracker
<http://bugs.python.org/is
James C. Ahlstrom added the comment:
I received a bug report from a user. He had a zip file created by Mac OS
10.5.8 that the zipfile module claimed was not a valid zip file. The traceback
went to function _EndRecData(fpin). The file had a valid comment appended, but
recorded a comment
James C. Ahlstrom added the comment:
Problem was reported on 2.7. I will check in detail this weekend. Please
stand by.
--
___
Python tracker
<http://bugs.python.org/issue1757
James C. Ahlstrom added the comment:
I grabbed a 2.7.2 zipfile.py, and my original comments stand. If there is a
"garbage at end of file" patch, I can't find it; please provide a line number
or a hint. The user at yale.edu reports that the patch works. Here is a diff
of
James C. Ahlstrom added the comment:
For completeness, I checked other versions of Python. The example zip file
fails in Python 3.1, but succeeds in Python 3.2.2. The patch for 3.2.2 removed
the check for correct comment length, but substituted no further check for
validity
James Y Knight added the comment:
Oh wow, so it depends on the *build* time major version? That's really not
useful at all for linux 2.x and 3.x; there is nothing useful anyone can
possibly do with the distinction between platform == "linux2" and platform ==
"linux3&quo
James Y Knight added the comment:
> I will backport the fix to 2.7 and 3.2.
Uh, wait, so does that mean you're *not* going to do the
compatibility-preserving thing and force sys.platform to stay linux2 even when
python is built (BUILT! not run!) on a machine where the active kernel
James Y Knight added the comment:
> Well, except maybe if you plan to write applications working only on Python
> >= 2.7.3? ... this version is not released yet.
No, of course I don't plan on writing new code that checks sys.platform ==
'linux2'. That's ridicu
James Y Knight added the comment:
M.A., your comments do not make sense in the context of Linux. It does not
actually require porting -- Linux 2.6.39 to Linux 3.0 is no more disruptive
than Linux 2.6.38 to Linux 2.6.39. *Except* that python ill-advisedly exported
a "platform" st
James Y Knight added the comment:
> Sure, you can compile and run Python on both versions of Linux, but
> what if your application uses features that are only present in Linux
> 3.0 and later ?
This comment is making me think you've missed just how irrelevant kernel
version 3.0
James Y Knight added the comment:
YAGNI. Nobody has needed sys.build_platform yet. (And no, sys.platform isn't
it, since that's been fixed at linux2 approximately forever). Why do you think
people would suddenly start needing to know the build-time kernel v
James Y Knight added the comment:
> configure_linux2.python3.2.patch
It would probably be more future-proof to use "linux*)", not "linux3)" in the
case expression.
--
___
Python tracker
<http://
James Eric Pruitt added the comment:
> Also, why is the result put in parens?
Without them, something like 'eval("100 * " + repr(imaginary))' would not work
properly.
--
nosy: +ericpruitt
___
Python tracker
<http://
James Y Knight added the comment:
I just ran into the impl of escape after being surprised that '/' was being
escaped, and then was completely amazed that it wasn't just implemented as a
one-line re.subn. Come on, a loop for string replacement? This is *in* the
freaking re mo
James Y Knight added the comment:
Show your speed test? Looks 2.5x faster to me. But I'm running this on python
2.6, so I guess it's possible that the re module's speed was decimated in Py3k.
python -m timeit -s "$(printf "import re\ndef es
James Y Knight added the comment:
Right you are, it seems that python's regexp implementation is terribly slow
when doing replacements with a substitution in them. (fixing the broken test,
as you pointed out changed the timing to 97.6 usec vs the in-error-reported
18.3usec.)
Oh we
New submission from James William Pye :
Basically, nested() doesn't seem to be consistent with explicitly nested
with-statements when an exception is thrown in a CM's __enter__.
Consider a pair of nested CMs, the inner __enter__ raises an exception
trapped by the outer. In the si
James William Pye added the comment:
I had actually forgotten that this was still open. Anything I can do to
help speed this along?
In case nobody remembers, the purpose of this was to provide a facility
to embedded applications that allows for a more graceful shutdown in
fatal error
New submission from James William Pye :
I found this bug by misplacing a line of a code. Yes, I was doing
naughty things, but in the case of the class that led to the discovery,
it was inadvertent. :P
class something_else(object):
pass
class foo(object):
def __del__(self):
self.__class__
New submission from Zayden Micheal James :
When I try to install numpy using python version 3.10, pip version 21.2.4
it gives me a PEP517 error, with a bunch of other exceptions.
When I try to install tensorflow using python version 3.10, pip version 21.2.4
it gives me an error saying that
Zayden Micheal James added the comment:
This issue is still persisting with other libraries aswell such as matplotlib
and the above mentioned.
--
nosy: -eric.smith
resolution: third party ->
status: closed -> open
type: compile error ->
Zayden Micheal James added the comment:
I am using Python 3.10 and PIP 21.2.4. All installations worked fine with
Python 3.9.
I tried combinations such as:
["pip", "pip3", "python3 -m pip", "python -m pip3", "python -m pip","python3
Zayden Micheal James added the comment:
Oh so the problem will resolve itself when they, support Python 3.10 PIP 21.2.4.
Sorry for the inconvenience. Can't wait for the libraries to be resolved and
optimized
--
___
Python tracker
&
Change by James B Wilkinson :
--
nosy: the.doc
priority: normal
severity: normal
status: open
title: I
___
Python tracker
<https://bugs.python.org/issue42
New submission from James B Wilkinson :
> On Dec 21, 2020, at 11:11 PM, Raymond Hettinger
> wrote:
>
>
> Change by Raymond Hettinger :
>
>
> --
> stage: -> resolved
> status: open -> closed
I see that this has been marked “resolved” and closed
New submission from David James Peters :
The ConfigParser().write() does not save the comments; this makes using
comments harder because it requires a separate demo ini file the user must be
able to locate and read from without learning anything from the INI file they
are using. Not Good. Pls
New submission from James Y Knight:
The change done for issue9291 in Python 2.7.7 caused the mimetypes.types_map
dict to change to contain a mixture of str and unicode objects, rather than
just str, as it always had before.
This causes twisted.web to crash when serving static files on Windows
James Y Knight added the comment:
Reverting the incorrect commit which caused the regression would be a good
start.
--
___
Python tracker
<http://bugs.python.org/issue21
James William Pye added the comment:
Seeing this in 3.1 when I try to compile with mingw32 under wine:
"error: Unable to find vcvarsall.bat"
--compiler=mingw32 works in 3.0. I assume it's related to this bug?
--
nosy: +jwp
versio
James William Pye added the comment:
Just downloaded v2 and tried it out against Python 2.7a0 (trunk:70381M,
Mar 14 2009, 23:12:51).
output of the "nested_issue.py" script with patch:
j...@torch[]:org/python/trunk 0% /src/build/py/bin/python ./nested_issue.py
()
[try_with_nested
James William Pye added the comment:
I tested the attached script against v2.
It further identifies consistencies between nested with-statements and
nested() that should exist(and do in v2). It answers the question: what
is the effect of a SkipStatement exception on another, outer CM?
with
James Eric Pruitt added the comment:
Hello, I am working on this patch and some additional features for my
Google Summer of Code project (subdev.blogspot.com) and will eventually
attempt to get the code committed to Python 3.1 or 3.2 and Python 2.7. I
will have the unit tests completed shortly
James Y Knight added the comment:
The reason it's a problem is because a "device" is everything other than a
socket, pipe, slave-side of tty, or file. That is, /dev/null, /dev/zero,
/dev/tty, psuedo-tty masters from openpty (e.g. for running subprocesses), etc.
I find it qui
James William Pye added the comment:
Would it be possible to require the embedding application to define the
Py_FatalError symbol?
Admittedly, it would be nice to not have the callback installation code. =\
--
___
Python tracker
<h
James William Pye added the comment:
I guess it seemed so unlikely that (C) extensions should be installing the
callback that installation should be restricted pre-Py_Initialize(); the area
completely controlled by the embedding app.
However, I have no strong attachment to that
Changes by James William Pye :
--
nosy: -jwpye
___
Python tracker
<http://bugs.python.org/issue1195571>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by James R Barlow :
--
pull_requests: +105
___
Python tracker
<http://bugs.python.org/issue5945>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from James G. sack (jim):
'2.5 (r25:51908, Apr 10 2007, 10:27:40) \n[GCC 4.1.2 20070403 (Red Hat
4.1.2-8)]'
unicode(None)
u'None'
This doesn't seem right, ;-)
Regards,
,,jim
--
components: Unicode
messages: 56628
nosy: jgsack
severity:
James G. sack (jim) added the comment:
(aside: Wow! that was a fast response to my posting!)
I'm not really sure what makes the most sense,
possibly:
- an exception
- u''
- None
but not u'None'; not a string of length 4. That's quite unexpected!
Regards,
..jim
James G. sack (jim) added the comment:
Here's more:
>>> unicode(object)
u""
There seems to be an call to repr() somewhere in the process.
This seems, at least to me, to violate the principle of least surprise, and
I'm thinking that unicode(x) ought to return Unic
James G. sack (jim) added the comment:
Martin v. Löwis wrote:
> Martin v. Löwis added the comment:
>
> Ok. This is not a bug, but by design. unicode(X)==unicode(str(X)) for
> most things, and str(X)==repr(X) for most things. repr(None)=='None',
> hence the result yo
New submission from James G. sack (jim):
The behavior of codecs utf_16_[bl]e is to omit the BOM.
In a testing environment (and perhaps elsewhere), a forced BOM is useful.
I'm requesting an optional argument something like
force_BOM=False
I guess it would require such an option in mul
James G. sack (jim) added the comment:
Feature Request REVISION
Upon reflection and more playing around with some test cases, I wish to
revise my feature request.
I think the utf8 codecs should accept input with or without the "sig".
On output, only the
James G. sack (jim) added the comment:
Later note: kind of weird!
On my LE machine, utf16 reads my BE-formatted test data (no BOM)
apparently assumng some kind of surrogate format, until it finds
an "illegal UTF-16 surrogate".
That I fail to understand, especially since it quits u
James G. sack (jim) added the comment:
re: msg56782
Yes, of course I can explicitly write the BOM. I did realize that after
my first post ( my-'duh' :-[ ).
But after playing some more, I do think this issue has become a
worthwhile one. My second post msg56780 asks that utf_8 be to
James G. sack (jim) added the comment:
OK, I will work on it. I have just downloaded trunk and will see what
I can do. Might be a week or two.
..jim
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
James G. sack (jim) added the comment:
Adam Olsen wrote:
> Adam Olsen added the comment:
>
> The problem with "being tolerate" as you suggest is you lose the ability
> to round-trip. Read in a file using the UTF-8 signature, write it back
> out, and suddenly nothi
New submission from James G. sack (jim):
The streamreader in utf_8_sig.py fails when asked to read a specified
bytelength of data that ends up in the middle of a multibyte utf8 code.
I will attached a atandalone unittest (which does work from autotest, but
doesn't use test_su
Changes by James G. sack (jim):
Added file: http://bugs.python.org/file8750/test_utf8sig_stream.py
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1444>
__
___
James G. sack (jim) added the comment:
re: msg57041, I'm sorry if I gave the wrong impression about interacting
with other programs. I started this feature request with some half-baked
thinking, which I tried to revise in my second post.
Anyway I'm most interested right now in lobb
James G. sack (jim) added the comment:
Oops, it looks like my patch may have broken test_partial in test_codecs. I
will try to figure out what the test_partial does in the next day or so,
unless someone else can add some insignt in the meantime.
.jim
James G. sack (jim) added the comment:
One additional clue: test_codecs succeeds in verbose mode but fails in non-
verbose mode (autotest "verbosity") .. I think. My eyes are getting
blurry. More tomorrow, I guess.
..j
__
Tracker <[EMAIL PROT
James G. sack (jim) added the comment:
I found the errror in my previous patch. It lacked a self.decode=.. line
in the StreamReader.decode elif branch.
I attach a replacement patch diff-u.py26_utf8sig (apply to the 2.6 version
of utf_8_sig.py. (If allowed, I will next remove the incorrect
James G. sack (jim) added the comment:
More discussion of utf_8.py decoding behavior (and possible change):
For my needs, I would like the decoding parts of the utf_8 module to treat
an initial BOM as an optional signature and skip it if there is one (just
like the utf_8_sig decoder). In fact
James G. sack (jim) <[EMAIL PROTECTED]> added the comment:
> Can you post an example that requires this code?
This is not a big issue, and it wouldn't hurt if it got declared "go away
and come back later if you have patch, test, docs, and a convincing use
case".
New submission from James G. sack (jim) :
Docs for 2.6.2 (http://docs.python.org/library/random.html?
highlight=random#module-random)
presently say
"""
random.randint(a, b)
Return a random integer N such that a <= N <= b.
"""
It should say
...a <= N &l
New submission from James G. sack (jim) :
file Lib/tests/regrtest.py
Evidently rev 76260 (trunk) / 76261 (py3k)
broke code at
rev 76324 line 655 (py3k)
rev 76321 line 620 (trunk)
which is
if tests[0] == alltests[i]
because tests was rebound from a list to an iterable, and hence
James G. sack (jim) added the comment:
It seems that on my Fedora 11 AMD X86_64, the problem still exists. In
test_codecs.UTF32Test, test_handlers() seems to run forever, gobbling
memory to 99+% and then activating swap until it fills up swap.
tested by
svn up -r 74869
rm /tmp
James G. sack (jim) added the comment:
Clarification of my last message (msg96468):
The test_handler in the current revision (76850) also exhibits the same
memory-gobbling behavior. I only refered to -r 74869 because that's where
the test was introduced, ostensibly to verify the pat
James G. sack (jim) added the comment:
On my Fedora 11 AMD x86_64 system, it appears the deadlock still occurs
(up to the limit of my patience, ie: several minutes). If I reduce to say
3, I can get the test to succeed sometimes.
Observed in: trunk
-r 76850 (latest)
-r 75818 (first
James G. sack (jim) added the comment:
Thanks, it seems to work now.
My test method uses the command format
./python -Ebb Lib/test/regrtest.py -s test_calendar
Sorry for the delayed response, I discovered problems with
test_bz2
test_codecs
which I wanted to confirm was real rather
James G. sack (jim) added the comment:
Update: I was doing something wrong and getting false failures.
I forgot to do ./configure and make after major revision-switches so the
failures I was seeing in bz2 and codecs (and others, :-[ ) was bogus.
Repeating the main message, though:
The
James G. sack (jim) added the comment:
IMPORTANT Correction: Please disregard msg96472.
I was forgetting to do .configure and make, and evidently getting bogus
failures.
test_bz2 works fine now, ..sorry for the false alarm.
~jim
--
___
Python
James G. sack (jim) added the comment:
IMPORTANT Correction: Please disregard msg 96468 & 96470.
I was forgetting to do ./configure and make, and evidently getting bogus
failures.
test_codecs works fine now, ..sorry for the false alarm.
James G. sack (jim) added the comment:
test_commands test_getstatus also fails on linux with SELinux enabled
On gnu/linux, info ls reports:
"""
Following the file mode bits is a single character that specifies
whether an alternate access method such as an acce
New submission from James G. sack (jim) :
With -r 76870, on Fedora 11, amd x80_64, regrtest of test_format fails
when the -j option is combined with the -v option. It happens whether
testing everything or just the one test.
./python -Ebb Lib/test/regrtest -j3 -vv
or
./python -Ebb Lib
501 - 579 of 579 matches
Mail list logo