Mark Dickinson added the comment:
It would be nice to change 'arguments' to 'argument' in this case, too. :-)
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16515
___
Joril added the comment:
It looks like the test just walks a directory recursively while trying to
identify its files, there's no classic test of the this is a JPEG, is it
detected correctly-type
--
___
Python tracker rep...@bugs.python.org
Marco Amadori added the comment:
2012/11/21 Carl Meyer rep...@bugs.python.org
Carl Meyer added the comment:
Here is the bug filed against virtualenv that led to the addition of the
local/ directory: https://github.com/pypa/virtualenv/issues/118
As Vinay pointed out, the original fix was
New submission from Chris Jerdonek:
The TypeError message when a call to subprocess.Popen() lacks the args argument
is incorrect.
For 3.3 and 3.4, the message incorrectly says that a positional argument is
required when a keyword argument will do:
import subprocess
subprocess.Popen()
Mark Dickinson added the comment:
I don't think the first part of the report has anything to do with
subprocess.Popen:
def f(x):
... return
...
f()
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: f() missing 1 required positional argument: 'x'
See the
Chris Jerdonek added the comment:
Also see the terminology-related issue 15990 created from that thread.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16520
___
Trung Doan added the comment:
Suggestion: When Python is installed, it starts its configurations files
afresh.
Trung Doan
===
On Wed, Nov 21, 2012 at 8:54 AM, Serhiy Storchaka rep...@bugs.python.orgwrote:
Serhiy Storchaka added the comment:
Patch updated. Added warning for case when
Ezio Melotti added the comment:
+ hg resolve -am # needed only if the merge created conflicts
IIUC it's necessary, but only if you had a conflict and hg didn't invoke a
3-way merge tool. Here I use kdiff3, and I rarely have to use hg resolve.
--
New submission from Jovik:
Using logging.basicConfig() with Python 3.2.3 accepts handlers options without
any errors. It creates an empty file. I don't think this should be default
behaviour, sice it's very missleading (no exception thrown; no warning on
standard output or in the file)
R. David Murray added the comment:
Yes, so I suppose you could add a footnote that says using a three way merge
tool generally makes this step unnecessary.
Is there a bug report for this on the mercurial tracker? If so we could link
to the bug report :)
--
Chris Jerdonek added the comment:
Is there a bug report for this on the mercurial tracker?
Indeed there is -- by one of our own in fact :)
http://bz.selenic.com/show_bug.cgi?id=2706
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
Chris Jerdonek added the comment:
Here is a proposed patch just to get the ball rolling on this.
Note that I'm proposing that we let ourselves use the word standard in place
of positional-or-keyword when talking about parameters. This is partly
inspired by PEP 362, which says,
Chris Jerdonek added the comment:
Attaching new patch incorporating David's suggestions.
--
Added file: http://bugs.python.org/file28062/issue-16517-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16517
Kristján Valur Jónsson added the comment:
Code objects can indeed be shared.
One thing that the recode module does, or allows you to do, is to strip file
and line number information from code objects. This will theoretically allow
them to be collapsed.
Martin, I agree the .pyc size matters.
Roundup Robot added the comment:
New changeset 5c39e3906ce9 by Chris Jerdonek in branch '3.2':
Fix label in docs (from issue #13538).
http://hg.python.org/cpython/rev/5c39e3906ce9
--
___
Python tracker rep...@bugs.python.org
New submission from R. David Murray:
When debugging using tests or doing test driven development, I find it very
useful to have the test run exit immediately on the first failure. Doctest
currently has a feature to suppress all output after the first failure, but not
to exit on the first
New submission from R. David Murray:
It looks like the use of the 'args' formal parameter was cut and pasted from
the methodcaller docs, when it is not appropriate for itemgetter and attrgetter.
http://docs.python.org/3/library/operator.html#operator.attrgetter
--
assignee:
Ezio Melotti added the comment:
On one hand it's good to have individual entries that can be referenced.
On the other hand I think it's important that people get the full picture, and
having these definitions sparse in 4 or more distinct glossary entries doesn't
help IMHO -- even if the reader
Changes by Éric Araujo mer...@netwok.org:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16523
___
___
Python-bugs-list mailing
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16515
___
Almar Klein added the comment:
Just checking in to point out a possible problem with the code that strips the
MSVCR dependency from the embedded manifest. The used regexpr is too greedy:
the first bit can trigger on an earlier assemblyIdentity tag, so that after
the removal the manifest is no
Ezio Melotti added the comment:
Attached an initial patch:
max()
TypeError: max() requires at least a positional argument
max(foo=3)
TypeError: max() requires at least a positional argument
max(3, foo=3)
TypeError: max() got an unexpected keyword argument
max(3, 4)
4
--
keywords:
New submission from Antoine Brodin:
I have a file:
dir c:\Windows\System32\scext.dll
14/07/2009 02:4189 088 scext.dll
With Python 32 bits it fails:
c:\Python27\python.exe
Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on
win32
Type help, copyright,
Tim Golden added the comment:
Not Python, but Windows. See here:
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa384187%28v=vs.85%29.aspx
--
nosy: +tim.golden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16524
Antoine Brodin added the comment:
Ok, with Python 32 bits I can do:
os.stat('c:\windows\sysnative\scext.dll')
nt.stat_result(st_mode=33206, st_ino=0L, st_dev=0, st_nlink=0, st_uid=0,
st_gid=0, st_size=89088L, st_atime=1247527874L, st_mtime=1247535713L,
st_ctime=12475278
74L)
I will try to
Mark Dickinson added the comment:
Would it make sense to adjust the error messages in PyArg_UnpackTuple instead?
I suspect there are quite a lot of functions using it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16515
Ezio Melotti added the comment:
PyArg_UnpackTuple could be fixed to say positional argument (see attached
patch (maybe this should be a separate issue)).
The error returned by max() is wrong because PyArg_UnpackTuple is used on the
*args alone first, and it has no knowledge of the kwargs.
If
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16520
___
Mark Dickinson added the comment:
By the way, I think this message from Nick is the closest to a resolution from
that thread:
We've already had this terminology discussion and documented the results in
PEP 362. The rest of the docs may require updates to be brought in line with
that.
Mark Dickinson added the comment:
Yes, true: max is probably still going to have to be a special case, thanks to
its schizophrenic signature. (max([1, 2, 3]) versus max(1, 2, 3)).
--
___
Python tracker rep...@bugs.python.org
Chris Jerdonek added the comment:
TypeError: __init__() missing 1 required positional argument: 'args'
I think something like the following would be more correct:
__init__() missing argument for parameter 'args'
--
___
Python tracker
Daniel Urban added the comment:
I've added some tests and documentation. English is not my first language, so
the docs almost certainly need some correction.
--
nosy: +daniel.urban
Added file: http://bugs.python.org/file28066/doctest_fail_fast_2.patch
Changes by Daniel Urban urban.dani...@gmail.com:
Removed file: http://bugs.python.org/file28066/doctest_fail_fast_2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16522
___
Daniel Urban added the comment:
I'm sorry, I forgot the versionadded directive. The fixed patch is attached.
--
Added file: http://bugs.python.org/file28067/doctest_fail_fast_3.patch
___
Python tracker rep...@bugs.python.org
Carl Meyer added the comment:
What OS are you on, Marco?
It looks to me like pyvenv probably does need the same hack as virtualenv here,
to deal with OSes who set posix_local as the default installation scheme.
--
___
Python tracker
Roundup Robot added the comment:
New changeset 966432a0734c by R David Murray in branch 'default':
#16522: Add FAIL_FAST flag to doctest.
http://hg.python.org/cpython/rev/966432a0734c
--
nosy: +python-dev
___
Python tracker rep...@bugs.python.org
R. David Murray added the comment:
Looks great, I didn't think any changes were needed. Thanks a bunch, Daniel.
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
New submission from Sebastian Kraft:
The wave module cannot read audio WAV files containing 32bit float values. This
is a very common file type for professional audio!
There has already been a patch some years ago which works fine but was finally
not applied. I can confirm that it does not
Marco Amadori added the comment:
On Wednesday 21 November 2012 21:32:57 Carl Meyer wrote:
Carl Meyer added the comment:
What OS are you on, Marco?
Linux. Debian GNU/Linux amd64 sid/experimental.
It looks to me like pyvenv probably does need the same hack as virtualenv
here, to deal with
Christian Heimes added the comment:
HMAC-SHA3 hasn't been standardized yet. I'm not even sure their will be an
official HMAC-SHA3 standard anytime soon. Keccak uses a sponge design that
isn't vulnerable to length extension attacks like Merkle–Damgård based hashing
algorithms (MD5, SHA-1,
Changes by Berker Peksag berker.pek...@gmail.com:
--
versions: -Python 2.6, Python 3.1, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16525
___
New submission from Lothsahn:
Python doesn't really support cross compilation. I've created a patch for
Python 2.7.3 which compiles nearly all of Python (except a couple modules).
Patches for Python 3 are also included, but I didn't have anything to do with
them.
My patch allows for cross
New submission from Alexis Daboville:
Hi,
It looks like using a very long list of elif makes CPython segfault. You can
try it with the attached file, which looks like this:
if False:
pass
elif False:
pass
# thousands of elifs
elif False:
pass
$ python elif_segfault.py
Changes by Alexis Daboville alexis.dabovi...@gmail.com:
--
components: +Interpreter Core
type: - crash
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16527
___
Christian Heimes added the comment:
Nice catch! How did you notice the issue? I hope you didn't use thousands of
elifs in some code. It's going to perform horrible slow with O(n).
I'll see if we can fix the problem easily. As this is clearly a pathological
case I consider a patch as nice to
Christian Heimes added the comment:
Interesting, a debug build of Python doesn't segfault.
$ 3.3/python elif_segfault.py
RuntimeError: maximum recursion depth exceeded during compilation
[41897 refs]
$ python3.3 elif_segfault.py
Speicherzugriffsfehler (Speicherabzug geschrieben)
Backtrace:
#0
Alexis Daboville added the comment:
I had the feeling that there was a possible issue when reading how elifs were
represented in the AST. I'm not insane enough to write so many elifs in a real
program ;).
I totally agree on the 'nice to have' part rather than 'required'.
--
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16517
___
___
Python-bugs-list mailing list
Jesús Cea Avión added the comment:
This is a new feature. Targeting Python 3.4.
--
nosy: +jcea
versions: -Python 2.7, Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16525
Changes by Jesús Cea Avión j...@jcea.es:
--
superseder: - wave file module does not support 32bit float format
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1144504
___
Jesús Cea Avión added the comment:
Can somebody point to a floating point WAVE specification?.
I think the issues raised in the original bug still stands. Also, support for
writing should be provided too.
Jesús Cea Avión added the comment:
This is 3.4 material.
Could you possibly work with us to properly integrate in 3.4?.
--
nosy: +jcea
versions: +Python 3.4 -Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16527
___
___
Python-bugs-list mailing list
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16507
___
___
Python-bugs-list mailing list
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16510
___
___
Python-bugs-list mailing list
Kiet Tran added the comment:
I was trying to fix this, but I ran into a couple questions.
1) Once I put, say, x + y and x - y into the same table cell, what would a
good format be? My preferred format is to have them on separate lines in the
cell, but after a lot of googling on the syntax of
Chris Jerdonek added the comment:
Addressed by: http://hg.python.org/devguide/rev/78a69b929ab7
(I accidentally left the issue number out of the commit message.)
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
New submission from Chris Jerdonek:
The 3.2 docs haven't updated since Oct 28, 2012:
http://docs.python.org/3.2/
The commits for the Doc folder around that time are as follows. I observed
that the top commit was not built, but I'm not sure about the ones previous:
$ hg log -b 3.2 Doc | more
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16514
___
___
Python-bugs-list mailing list
R. David Murray added the comment:
This is intentional. Only 2.7, 3.3, and 3.4 auto-update now that 3.3 is out.
There will be a final rebuild of the 3.2 docs when 3.2 final is released.
--
nosy: +r.david.murray
resolution: - invalid
stage: - committed/rejected
status: open - closed
Chris Jerdonek added the comment:
I like option (3). I attached a new patch using this approach.
As suggested, I made the glossary entries for keyword argument and
positional argument into stubs. So now there are just two substantive
entries: one for argument and one for parameter. I also
Chris Jerdonek added the comment:
Thanks for the info. Is this information reflected somewhere online?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16528
___
Meador Inge added the comment:
Attached is a refreshed patch that works for all active branches. The only
real change from the original is Éric's suggestion to s/hash/hashlib/. The 'u'
prefix isn't an issue any longer because of PEP 414.
Benjamin, does the attached look OK to you? If so,
Todd Rovito added the comment:
Attached is patch with the final formatting for the documentation updates. I
fixed the :exc:`OSError` problems that I had before and used indents to denote
Unix behavior VS Windows behavior. Please let me know if I can do anything else
to help get this issue
Changes by Todd Rovito rovit...@gmail.com:
Removed file: http://bugs.python.org/file27640/OSRenameTest3point4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16278
___
Roundup Robot added the comment:
New changeset bf1bf3bf3fe2 by Éric Araujo in branch '3.3':
Address reviews for open’s opener argument doc patch (#13424).
http://hg.python.org/cpython/rev/bf1bf3bf3fe2
New changeset 8ca6f4953c4b by Éric Araujo in branch 'default':
Merge #13424 followup from 3.3
Éric Araujo added the comment:
Thanks for all comments. If you think of a better example to show the usage of
the argument, feel free to change it.
--
assignee: docs@python - eric.araujo
resolution: - fixed
stage: commit review - committed/rejected
status: open - closed
Éric Araujo added the comment:
Is it impossible to edit the install scheme when run in a venv, so that the
workaround becomes unnecessary? We are the upstream after all :)
--
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
Yongzhi Pan added the comment:
One possible solution:
We do not list priorities of the operations, instead link to the precedence
table in the language reference.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16438
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16527
___
___
Python-bugs-list
70 matches
Mail list logo
