New submission from Jim Jewett:
http://docs.python.org/3.4/library/email.html#package-history
The table ends with email version 5.1, distributed with Python 3.2, and
compatible with Python 3.0 to 3.2.
Since Python 3.3 and 3.4 also distribute 5.1.0, I'm betting that the actual
compatib
Jim Jewett added the comment:
OK, if I understand *that* correctly,
(1) The locking mechanism doesn't really work, and that is too complicated to
fix in this issue. A new issue would be fine.
(2) The locking failure messes up the Table Of Contents, but that is too
comprehensive a c
Jim Jewett added the comment:
I have now also looked at cgi-doc.patch, and it is not strictly documentation
changes. I have no informed opinion on the the additional changes, but I don't
think they should go in as "doc change".
--
___
New submission from Jim Peterson:
The result returned by somenamedtuple._source seem inconsistent, in that it
defines __dict__ as:
__dict__ = property(_asdict)
even though it imports property as:
from builtins import property as _property
and the namedtuple fields are defined using
Jim Jewett added the comment:
_check_closed sounds like you expect it to be closed, and might even assert
that it is closed, except that you want the check run even in release mode
and/or it might fail. Since being closed is actually the unexpectedly broken
state, I would prefer that you
Jim Jewett added the comment:
I think the requested timing regression was for the non-broken case. When the
database has NOT been closed, and keys() still works, will it be way slower
than before?
Note that I am not asking you to do that test (though the eventual committer
might); the
Jim Jewett added the comment:
Pinging Martin ... earlier comments seem to have been completed.
--
nosy: +Jim.Jewett
___
Python tracker
<http://bugs.python.org/issue19
Jim Jewett added the comment:
ProcessPoolExecutor already defaults to using cpu_count if max_workers is None.
Consistency with that might be useful too. (and a default of 1 to mean
nothing in parallel is sensible...)
--
nosy: +Jim.Jewett
Jim Jewett added the comment:
I confirm the bug.
The patch looks good.
--
nosy: +Jim.Jewett
___
Python tracker
<http://bugs.python.org/issue21362>
___
___
Pytho
Jim Jewett added the comment:
pinging David Watson: What is the status? If I understand correctly, (and I
may well not), you have already opened other issues for parts of this, and
(only) the final patch is ready for patch (and hopefully) commit review. Is
this correct
Jim Jewett added the comment:
I don't know for sure if the compatibility claims are correct, but the patch
looks good.
--
stage: -> commit review
___
Python tracker
<http://bugs.python.org
Jim Jewett added the comment:
Trying to put bounds on the disagreements. Does anyone disagree with any of
the following:
(1) compileall currently runs single-threaded in a single process.
(2) This enhancement intends to allow parallelization by process.
(3) Users MAY need to express
Jim Jewett added the comment:
I'm leaving it as "needs patch" because it isn't clear exactly what a committer
should do.
I think the current intent is to make the changes listed in
zipfile_???_filename_mismatch_v2.patch (which are not listed as reviewable --
but th
Jim Jewett added the comment:
Presumably the stacklevel applies to all versions; verifying that it warns
about the right code location is important enough to require a test case.
--
___
Python tracker
<http://bugs.python.org/issue6
Jim Jewett added the comment:
On Wed, Apr 30, 2014 at 3:05 PM, Adam Polkosnik wrote:
> test.zip up there is the test case for this change. Is there any other test
> case needed?
ah; I see the confusion. test.zip is test *data*. When I asked for a
test *case*, I meant something that e
Jim Jewett added the comment:
On Wed, Apr 30, 2014 at 3:11 PM, Adam Polkosnik
> I've got some test cases where the zlib_forward_slash.patch doesn't cut it.
My recommendation (and I could be convinced otherwise) would be to replace
if fname_str != zinfo.orig_filename:
Jim Jewett added the comment:
On Fri, May 2, 2014 at 1:14 AM, Adam Polkosnik
> The problems documented here are related to two cases (both apparently
> arriving from world of windows):
Good! I had thought you had even more!
> 1. two relative paths with inverted slash in one of t
New submission from Jim Minter:
Python 3.3.2 (default, Mar 5 2014, 08:21:05)
[GCC 4.8.2 20131212 (Red Hat 4.8.2-7)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import email.header
&g
Jim Jewett added the comment:
Did you try 3.5 without the patch, in case the issue is not with his code?
On May 13, 2014 7:23 AM, "Serhiy Storchaka" wrote:
>
> Serhiy Storchaka added the comment:
>
> Claudiu, your benchmark is broken, it measure a no-op.
New submission from Jim Garrison:
As of Python 3.2, `os.makedirs()` takes `exist_ok` as a keyword argument. If
set to true, the function does not raise an error if the directory already
exists. This makes the function's behavior similar to `mkdir -p` on the UNIX
commandline. (See
Jim Jewett added the comment:
I'm still not seeing why these changes are sufficiently desirable to justify
the code churn. Nor am I seeing test or doc changes that would explain the
advantages of the new way, and prevent future regressions.
I agree that the changes would make the signa
Jim Jewett added the comment:
I think the new wording is an improvement, but keeping the changes minimal left
it in an awkward in-between state.
Proposal:
A string is a sequence of Unicode code points. Strings can include any
sequence of code points, including some which are semantically
Jim Jewett added the comment:
And even my rewrite showed path dependency; a slight further improvement is to
re-order encoding ahead of bytes. I also added a paragraph that I hope answers
the speed issue.
Proposal:
A string is a sequence of Unicode code points. Strings can include any
Jim Jewett added the comment:
Following up on Mark Lawrence's comment: http://bugs.python.org/issue12572 is
collecting the patches required to compile under HP/UX, and the patch there
supersedes those on this issue. Closing.
--
nosy: +Jim.Jewett
resolution: -> duplicat
Jim Jewett added the comment:
Added version 3.5; is 3.4 somehow still correct?
Set stage to patch review as there are still comments to deal with, but it
looks pretty close to commit review.
--
nosy: +Jim.Jewett
stage: -> patch review
versions: +Python
Jim Jewett added the comment:
As best I can tell, this renames the original get_code to _get_code, and then
delegates to it after handling the imp.PY_FROZEN case ... why not just add
imp.PY_FROZEN to the if/elif chain in the original method?
I also note that the call to self._fix_name doesn&#
Jim Jewett added the comment:
I agree with R. David Murray, but it may be worth adding a clarification
sentence (or an example with sorted) to the documentation.
Changing status to Pending, in hopes that any doc changes would be quick.
--
nosy: +Jim.Jewett
resolution: -> not a
Jim Jewett added the comment:
(1) The patch is just to docs, not code, so I'm not entirely sure that I
understood it properly.
(2) The new semantics are a huge mess to explain. This might be because the
old semantics were bad, but the result is the same. I think it would be bette
New submission from Jim Jewett:
Inspired by https://mail.python.org/pipermail/python-dev/2014-June/135029.html
and the following thread.
"""
Normal Windows behavior:
>hg status --rev ".^1"
M mercurial\commands.py
? pysptest.py
>hg status --rev .^
Jim Jewett added the comment:
Removing the existing behavior will almost certainly not be accepted, because
of backwards compatibility.
Adding new functionality is generally acceptable.
Doing that through a new keyword that defaults to the old behavior is fairly
common, and generally better
Jim Jewett added the comment:
On Jun 14, 2014 4:05 AM, "Aymeric Augustin"
> preserving the same behavior by default
That is a requirement, because of backwards compatibility.
> providing more control for users who need a different behavior, for
instance people who use SQLite a
New submission from Jim Pattee:
Python 3.3 Permission Error with User Library on Windows
I have certain scripts that run without error on Python 2.7 and 3.2. With
Python 3.3 they get a "Permission Error". This does not occur with every
script. The difference seems to be that the o
Jim Pattee added the comment:
Python 3.3 (64bit)
Traceback (most recent call last):
File "file-py\astyle-protected.py", line 157, in
process_files()
File "file-py\astyle-protected.py", line 30, in process_files
get_header_variables(header_variables, header_p
Jim Pattee added the comment:
The problem is not file permissions nor the install. I did some further testing.
The problem actually occurs with the library calls at lines 23 and 25. I
changed these lines to eliminate the library call by just hard coding the file
path.
Change from:
line 23
Jim Pattee added the comment:
You have been in contact with my friends at Mensa.
Further information:
Just branching into the library causes a problem with permissions when opening
files, even if the library just immediately returns.
Opening the file in the library, before returning to the
New submission from Jim Minter:
sqlite3 doesn't populate the lastrowid member of the Cursor object when a SQL
REPLACE statement is executed.
The following snippet doesn't work as I would expect:
cursor = db.execute("REPLACE INTO table(column) VALUES ('datum')")
pr
Jim Jewett added the comment:
These comments refer to
http://hg.python.org/cpython/file/5c9af8194d3b/Doc/library/tracemalloc.rst
which is newer than the current patches.
I believe I have consolidated the still-open issues that I see (including those
that aren't mine) for this file:
Jim Jewett added the comment:
Drat: forgot one at line 277
.. function:: get_traced_memory()
Get the current size and maximum size of memory blocks traced by the
:mod:`tracemalloc` module as a tuple: ``(size: int, max_size: int)``.
I have a tendency to read "maximum size" a
Jim Jewett added the comment:
It would be good to have the library work unchanged on both implementations.
If subprocess only failed later, it would be less good, as the stdlib would
then set an example that doesn't actually succeed.
Note that the attached patch (by flox) does NOT impl
Jim Jewett added the comment:
(The above concerns -- other than whether it is sufficient to work -- do not
apply to the change at
https://bitbucket.org/ironpython/ironlanguages/commits/b6bb2a9a7bc5/ )
--
___
Python tracker
<http://bugs.python.
Changes by Jim Jewett :
--
stage: -> needs patch
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue21800>
___
___
Python-bugs-list
New submission from Jim Jewett:
https://docs.python.org/3.5/library/stdtypes.html
says "Objects of different types, except different numeric types, never compare
equal."
Despite the location, this seems to strong a statement, because of subclasses
and classes which define __eq__
New submission from Jim Jewett:
https://docs.python.org/3.5/reference/expressions.html#not-in
Containers are permitted to (and generally do) read "same as" as "is or
__eq__), which can be confusing -- particularly in the section defining __eq__.
Several suggested changes:
Jim Jewett added the comment:
Ah... "be the same object or compare equal" sounds much better.
I don't want "same" to sound like an informal wording for equal, because
getting rid of the confusion over NaN and similar objects is the whole
point of the revision. On the
New submission from Jim Conyngham:
Python will not install on my Windows 7 (64-bit) OS.
I have repeatedly tried the install with variations (specifying an install
directly vs. taking the default; running as admininstrator vs. not; with and
without logging) and with multiple downloads python
New submission from Jim Carroll:
On the page
https://docs.python.org/2/extending/embedding.html#compiling-and-linking-under-unix-like-systems
The documentation makes the following reference:
"...(use sysconfig.get_makefile_filename() to find its location)..."
But this is incorrect.
New submission from Jim Carroll:
When building Python 2.7.6 on older GCC 2.x, the _ctypes module fails to build.
The failure is caused due to a header file reference to __builtin_expect (the
author expected this to be available when the module was built with gcc, but
did not take into account
Jim Carroll added the comment:
As requested, I've opened the issue with the libffi project:
https://github.com/atgreen/libffi/issues/63
--
___
Python tracker
<http://bugs.python.org/is
Jim Jewett added the comment:
Many people will not realize that the interactive help is affected by inspect
or pydoc; it would be courteous to mention this.
(Viewing
http://docs.python.org/dev/whatsnew/3.4.html#summary-release-highlights )
In the highlights (table of contents?) section
Jim Jewett added the comment:
I do not think it is sufficient to mention the help change under "Other
Language Changes", because the people who know to look at that level of detail
(let alone that particular location) are not the ones who will b
Jim Jewett added the comment:
"(If the installation has Internet access, it is of course possible to upgrade
pip to a release more recent than the bundled pip by using the bundled pip
command itself once it is installed.)"
-->
"(If the installation has Internet acces
Jim Jewett added the comment:
"wave can now write output to unssekable files. "
-->
"wave can now write output to unseekable files. "
--
___
Python tracker
<http://
Jim Jewett added the comment:
Changes in the Python API:
"If you use pyvenv in a script and desire that pip not be installed, you must
add --wihtout-pip to your command invocation."
-->
"If you use pyvenv in a script and desire that pip not be installed, you must
add --w
Jim Garrison added the comment:
Also needed here. While pretty-printing should be able to insert
non-significant whitespace BETWEEN xml elements, it should never alter
the content of (i.e. insert whitespace into) existing text elements.
--
nosy: +jgarrison
Jim Garrison added the comment:
To clarify:
... it should never alter the content of (i.e. insert whitespace into)
existing text elements that contain non-whitespace characters.
--
___
Python tracker
<http://bugs.python.org/issue4
New submission from Jim Fulton :
I've attached a script that demonstrates the problem. When run with
Python 2.5, it outputs statistics. When run with Python 2.6.2 it
generates a TypeError:
python2.6 hotshotbug.py
Traceback (most recent call last):
File "hotshotbug.py&qu
Jim Fulton added the comment:
Fred might be interested. :)
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue6710>
___
___
Python-bugs-list mailin
Changes by Jim Baker :
--
nosy: +jbaker
___
Python tracker
<http://bugs.python.org/issue4111>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Jim Jewett added the comment:
I would try to make it more explicit that updates do not reset the
order, but deleting a item and re-inserting it *does*. (So it isn't
the first insertion of the key, it is the first that hasn't yet been
followed by a deletion.)
Maybe change:
Jim Jewett added the comment:
I would also recommend strengthening some of the tests with regard to
ordering stability across update vs delete-and-reinsert.
TestOrderedDict.test_update does verify that updated items are not
moved to the end, but the comment suggests it is only checking that
New submission from Jim Jewett :
Copy of issue 5397
In python 3, UserDict (and DictMixin) are gone; presumably they should
be replaced by either a dict subclass or the ABC MutableMapping.
Unfortunately, there doesn't seem to be a clean way to inherit from
both.
In python 2.x, you
Jim Blandy added the comment:
In case the behavior requested here is controversial, here's an example
of where it would be nice to have relpath(x, '/') return a path for x
that is relative to the root directory:
The 'oprofile' system profiler for Linux profiles everyth
New submission from Jim Correia :
The module doc string contains an example with hex escape sequences (see
below). They are converted to their literal values by pydoc, which
results in an unexpected encoding for the output of pydoc.
(raw string, or proper escaping solves the problem
New submission from Jim Olson :
import io
# Corrected a typo in Python261/Lib/io.py at line 1167
# return self.writer.closed() ==> return self.writer.closed
# in
#@property
#def closed(self):
#return self.writer.closed
#also: shouldn't ascii strings still work in Pyth
Changes by Jim Olson :
--
components: +Library (Lib)
___
Python tracker
<http://bugs.python.org/issue5568>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jim Fulton added the comment:
> Looking back, I think Zope and Medusa should have adopted and evolved
> their own copy of asynchat a long time ago...
This statement is puzzling. No big deal, but I'm curious why you say
this.
--
Jim Fulton added the comment:
For the record, afaict, Zope wasn't broken by this. Supervisor isn't
part of Zope.
--
___
Python tracker
<http://bugs.python.
Jim Fulton added the comment:
On Apr 2, 2009, at 1:27 PM, Guido van Rossum wrote:
>
> Guido van Rossum added the comment:
>
> [Guido]
>>> Looking back, I think Zope and Medusa should have adopted and
>>> evolved
>>> their own copy of asynchat a long
Jim Fulton added the comment:
On Apr 2, 2009, at 3:35 PM, Josiah Carlson wrote:
>
> Josiah Carlson added the
> comment:
>
> I'm not defending the documentation, I'm merely reposting it.
>
> The documentation for asyncore says, "The full set of meth
New submission from Jim Garrison :
Trying to build 3.1a1 on Fedora 9, the following extensions get skipped
even though the requisite packages are installed
_dbm
_gdbm
_hashlib
_sqlite3
_ssl
bz2
readline
zlib
New submission from Jim Dennis :
.../lib/python2.*/SocketServer.py in class DatagramRequestHandler
contains the following comment:
# XXX Regrettably, I cannot get this working on Linux;
# s.recvfrom() doesn't return a meaningful client address.
This is a poor way to documen
Jim Dennis added the comment:
Addendum:
What I said about the default sendto() in finish() causing a loop in
server_forever() was wrong. I'd seen that behavior in an experimental
variation of the code.
The exceptions raised (and deficiencies in documentation) are the
Jim Wilson added the comment:
It's been more than a year. I'll work a little longer on the
SetProperty(...) example, but here's the "confirming evidence".
A related problem is 1884, but I simply don't remember the context and
long ago deleted the code in disgust
Jim Wilson added the comment:
I hope this helps. It's Greek to me now.
--
Added file: http://bugs.python.org/file14002/bar.py
___
Python tracker
<http://bugs.python.org/i
Jim Wilson added the comment:
Well, I violated the admonition of the Great Satan: "PID_CODEPAGE must
be first." (or words to that effect). It turns out not to make a
difference. Revised (conforming) source attached.
--
Added file: http://bugs.python.org/file14
Jim Jewett added the comment:
There were a number of patches to support sharing of data between
unicode objects. (By Larry Hastings?) They were rejected because (a)
they were complicated, and (b) it was possible to provoke pathological
memory retention.
--
nosy: +jimjjewett
Jim Jewett added the comment:
Would this patch mean that users of pre-1.7 subversion would get build
failures? Is it possible to support both forms of wording?
--
nosy: +jimjjewett
___
Python tracker
<http://bugs.python.org/issue6
New submission from Jim Fulton :
In python 2.7 a module can't be used as a context manager.
For example, given the module, t.py:
def __enter__(*args):
print 'enter', args
def __exit__(*args):
print 'exit', args
In Python 2.6:
>>
Jim Fulton added the comment:
On Sat, Jul 10, 2010 at 4:08 PM, Éric Araujo wrote:
>
> Éric Araujo added the comment:
>
> Confirmed: http://docs.python.org/reference/datamodel#specialnames
> Closing. Sorry! (BTW, using import hackery and a custom module type, you
> could
Jim Jewett added the comment:
When I see a message like that, it normally means there is a firewall getting
in my way.
--
nosy: +Jim.Jewett
___
Python tracker
<http://bugs.python.org/issue28
New submission from Jim Nasby:
Attached patch fixes two comments in dictobject.c referring to no longer
exposed _PyThreadState_Current variable. I also tweaked the grammar for that
issue in NEWS, since it came up in my search. Apologies if that's considered
gratuitous
Jim Nasby added the comment:
This is still affecting me on 2.7, even with the new changes. 3.7 seems to be
OK (I'm getting a different error on 3.7, but it seems unrelated to this.)
OS X 10.11.6.
--
nosy: +Jim Nasby
___
Python tracker
Jim Nasby added the comment:
I take it back... turns out I was building with the unsupported macports gcc.
--
___
Python tracker
<http://bugs.python.org/issue29
New submission from Jim DeLaHunt:
I just had a problem with doctests. It manifested as an error that occurred
when I did
>>> import StringIO
in my doctest.
After some investigation, I realised that my actual problem was that the
doctest library documentation https://docs.python.org/
Jim DeLaHunt added the comment:
Marco, thank you for your prompt comment.
However,
> Maybe you are running the doctest with Python 3. The StringIO module is no
> more available in Python 3, so your doctest will fail on Python 3
Please let me be clear. This issue is not abo
Jim DeLaHunt added the comment:
Marco, thank you for the suggestion to watch Raymond Hettinger's talk.
> I suggest you to watch this talk of Raymond Hettinger, before going on:
>
> https://www.youtube.com/watch?v=voXVTjwnn-U
That video is 63 minutes long, and a lot of those min
Jim DeLaHunt added the comment:
Marco and David, thank you again for your prompt replies.
Let me respond to both of your comments on the doctest module documentation
itself.
[Marco] > The example in section 26.3.3.2 [1], before the compound statement
(the if/else), contains two sim
Jim DeLaHunt added the comment:
Marco, thank you for the suggestion of a howto. That is a good idea.
In parallel, I was thinking of some howto content that I would like to see
documented.
• How to decide what to test with doctests and what with unittests. I have a
feeling that the sweet
Jim DeLaHunt added the comment:
Marco:
> To have a wide view, usually it is a good idea to start from the beginning:
>
> https://groups.google.com/forum/#!msg/comp.lang.python/DfzH5Nrt05E/Yyd3s7fPVxwJ
Thank you, that is a very interesting thread. Clearly the creator of doctests,
T
New submission from Jim DeLaHunt:
The Eclipse IDE, and its relatives pydev and LiClipse, store settings in the
root of a repository. It would be nice for the master .gitignore file to ignore
these files, so that individual developers don't have to do this.
I am preparing a GitHub
Jim DeLaHunt added the comment:
A fix is in GitHub cpython PR #75.
--
pull_requests: +26
___
Python tracker
<http://bugs.python.org/issue29510>
___
___
Python-bug
Changes by Jim DeLaHunt :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue29510>
___
___
Python-bugs-list mailing list
Unsubscrib
Jim DeLaHunt added the comment:
I'm now looking at cpython as retrieved from Mercurial by Eclipse. It appears
to be concerned by the presence of
.project
which is also an Eclipse settings file.
It might be reasonable to extend the scope of this issue to include telling
Mercurial to i
Jim DeLaHunt added the comment:
gitignore_global is a great idea. I had not heard of it before.
But here it is: https://help.github.com/articles/ignoring-files/ . This
instruction also has a link to a gist with a lot of helpful global ignores.
I understand your reluctance to add entries for
Jim DeLaHunt added the comment:
I have set up a global gitignore, and it works for me.
% git config --global core.excludesfile ~/.gitignore_global
(Amusingly, I had _already- set a global gitignore, but I had forgotten it
existed, and it didn't ignore these IDE files.)
I agree that we s
New submission from Jim DeLaHunt:
When I build the documentation on the current CPython code, there is a
deprecation warning on the console.
= (beginning of output)
% make html
sphinx-build -b html -d build/doctrees -D latex_elements.papersize= .
build/html
Running Sphinx v1.5.2
New submission from Jim DeLaHunt:
When I build the documentation on the current CPython code, there are various
error and warning messages on the console.
Here's what my build output looks like. I've marked the messages I'm concerned
about with a numbered >>0>> p
Jim DeLaHunt added the comment:
The other warnings in the "make html" output are the subject of
http://bugs.python.org/issue29521 .
--
___
Python tracker
<http://bugs.python.o
Jim DeLaHunt added the comment:
Thanks, Martin, for your suggestions.
In Misc/NEWS, I've respelled the ``char *`` as you suggested.
In faq/windows.rst, I've used your wording from the discussion in
http://bugs.python.org/issue29387 .
Pull Request 76 https://github.com/python/cpyth
Jim DeLaHunt added the comment:
I just created Pull Request 76 https://github.com/python/cpython/pull/76 to
address http://bugs.python.org/issue29521 .
In faq/windows.rst, I've used your wording from the discussion in of this bug.
I may have address this issue completely, in fact.
301 - 400 of 742 matches
Mail list logo
