[issue20822] WINhelp file loads Table of Contents, but not contents: "Navigation to webpage cancelled"

[Nemo Neminibus]

New submission from Nemo Neminibus:

File: python334.chm
Downloads, md5sum correct.
MS help executable opens a page with Table of Contents, but also displays a box 
with following message: "Navigation to the webpage was canceled"
Clicking on any page icon in Table of Contents list produces no result.

--
components: Windows
messages: 212535
nosy: Nemo.Neminibus
priority: normal
severity: normal
status: open
title: WINhelp file loads Table of Contents, but not contents: "Navigation to 
webpage cancelled"
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20821] Should be able to break long numbers across lines

[Eric V. Smith]

Eric V. Smith added the comment:

Please discuss this on the python-ideas mailing list, then if there's interest 
we'll re-open this issue.

I'm -0 on the idea, but I haven't really thought about it much.

--
nosy: +eric.smith
resolution:  -> rejected
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20821] Should be able to break long numbers across lines

[Ryan Govostes]

New submission from Ryan Govostes:

I cannot find a way to break a long number across multiple lines, other than to 
write the number as a string, take advantage of string literal concatenation, 
and then convert the string to an integer.

I'd like to be able to write, for example,

N = 17976931348623159077293051907890247336179769789423065727343008115 \
77326758055056206869853794492129829595855013875371640157101398586 \
47833778606925583497541085196591615128057575940752635007475935288 \
71082364994994077189561705436114947486504671101510156394068052754 \
0071584560878577663743040086340742855278549092581

To support this, adjacent integer literals should be concatenated also.

I don't think this would introduce any backwards-compatibility issues.

My preference would be to require each literal be written with its prefix, 
e.g., '0xDEAD 0xBEEF'. It strikes me as poor style to mix different bases, 
e.g., '0xa 5'.

--
components: Interpreter Core
messages: 212533
nosy: rgov
priority: normal
severity: normal
status: open
title: Should be able to break long numbers across lines
type: enhancement
versions: Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20820] HTML being escaped on some release pages

[Ned Deily]

Ned Deily added the comment:

Sorry, you were pointed to the wrong tracer.  For problems with the new 
website, the tracker is:

https://github.com/python/pythondotorg/issues

But, as noted in a reply, the pages you cite should now render properly.  
Thanks for reporting it!

https://mail.python.org/pipermail/pydotorg-www/2014-March/002461.html

--
nosy: +ned.deily
resolution:  -> out of date
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20820] HTML being escaped on some release pages

[Nick Timkovich]

New submission from Nick Timkovich:

On a random trip through Python's past I noticed the new site is escaping HTML 
on some older version release notes:

* http://www.python.org/download/releases/1.6/
* http://www.python.org/download/releases/2.0/
* http://www.python.org/download/releases/2.1/
* http://www.python.org/download/releases/2.1.[1-3]/ (2.1.1, 2.1.2, 2.1.3)
* http://www.python.org/download/releases/2.2/
* http://www.python.org/download/releases/2.2.[1-2]/
* http://www.python.org/download/releases/2.3/
* http://www.python.org/download/releases/2.3.[1-5]/

I was pointed here from the pydotorg-www list, but None of the components seem 
to fit with website maintenance.

--
messages: 212531
nosy: nicktimko
priority: normal
severity: normal
status: open
title: HTML being escaped on some release pages
type: behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20819] reinitialize_command doesn't clear install_lib on install and install_lib commands

[Jason R. Coombs]

New submission from Jason R. Coombs:

The setuptools source references a "distutils bug" here: 
https://bitbucket.org/pypa/setuptools/src/85760c42740829000a19ebf708d0a9cd565bb0eb/setuptools/command/bdist_wininst.py?at=default#cl-7

>From what I infer from that message, the bug is that 'reinitialize_command' 
>doesn't clear the 'install_lib' property on the 'install' or 'install_lib' 
>commands.

I'm actually skeptical that setuptools even needs to clear the 'install_lib' 
property on the 'install_lib' command, for as best as I can tell, the 
install_lib command only ever sets install_dir.

Nevertheless, I wanted to log a ticket to reference in the code to ultimately 
find a solution rather than a workaround.

--
components: Distutils
messages: 212530
nosy: jason.coombs
priority: normal
severity: normal
status: open
title: reinitialize_command doesn't clear install_lib on install and 
install_lib commands
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20249] test_posix.test_initgroups fails when running with no supplementary groups

[Roundup Robot]

Roundup Robot added the comment:

New changeset 82bcc626ffd4 by Benjamin Peterson in branch '3.3':
fix test_posix.test_initgroups to work without supplemental groups (closes 
#20249)
http://hg.python.org/cpython/rev/82bcc626ffd4

New changeset 1fbec1c44911 by Benjamin Peterson in branch '2.7':
fix test_posix.test_initgroups to work without supplemental groups (closes 
#20249)
http://hg.python.org/cpython/rev/1fbec1c44911

New changeset a0abc7555d0e by Benjamin Peterson in branch 'default':
merge 3.3 (#20249)
http://hg.python.org/cpython/rev/a0abc7555d0e

--
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20815] ipaddress unit tests PEP8

[Nick Coghlan]

Nick Coghlan added the comment:

I'd suggest focusing more on the structured tests at the top of the file - the 
ones further down we largely incorporated wholesale from the original ipaddr 
project, and didn't go back and enforce PEP 8 compliance, but the new tests 
should follow the style guide.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Eric V. Smith]

Eric V. Smith added the comment:

I still think this is a special case that we won't "fix". And even if we did, 
you'd have to wait until 3.5.

But instead of your solution, it might be easier to wrap your floats in a class 
that implements your version of format, based on float's format with some 
post-processing:

class MyFloat(float):
def __format__(self, fmt):
s = float.__format__(self, fmt)
if s[1] == '0':
return s[0] + s[2:]
return s

print(format(MyFloat(0.12345678), '+8.8'))
print(format(MyFloat(1.12345678), '+8.8'))

gives:
+.12345678
+1.1234568

I've grossly simplified __format__, of course. And I'm using built-in format() 
instead of ''.format() (because it's less typing), but they use the same 
mechanisms. So:

print('{}:"{:+10.8}"'.format('answer', MyFloat(0.12345678)))

gives:
answer:"+.12345678"

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[aubmoon]

aubmoon added the comment:

That is exactly what I tried first. It turns out in the particular case I
have been working the 8th digit is needed for correct answers. The job is a
port of a punch card FORTRAN system into something more modern. The catch
is the system is a scientific application that protects life, limb, and
treasure. The new system must inter-operate with the legacy system until
the entire system can be replaced with VV&A software under configuration
control. In my particular case the sign must be printed, the decimal must
be printed, and all eight digits. The number is always strictly -1 < x < 1
and has eight significant digits. The number is the included in a larger
string of data. What I have done to address the issue is format the x
string separately from the rest of the data and then slice and join
out the undesired
leading 0. Then include the value as a %s format in the larger context.

On Saturday, March 1, 2014, Stefan Krah  wrote:

>
> Stefan Krah added the comment:
>
> aubmoon: Would it be a possibility just to use 'f' instead?
>
> >>> "{:+10.7f}".format(1.12345678)
> '+1.1234568'
> >>> "{:+10.7f}".format(0.12345678)
> '+0.1234568'
>
> --
> nosy: +skrah
>
> ___
> Python tracker >
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20465] Upgrade SQLite to 3.8.3 with 3.4.0 Windows and OS X installers

[Ned Deily]

Ned Deily added the comment:

"Fix a bug (ticket 4c86b126f2) that causes rows to go missing on some queries 
with OR clauses and IS NOT NULL operators in the WHERE clause, when the 
SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options are used."

http://www.sqlite.org/releaselog/3_8_3_1.html

We don't use those compile-time options for the OS X build, so, if this is the 
only meaningful bug, it may be a no-op.  The tests pass before and after.  
Still, it's probably better to update now.  I've opened Issue20818 as a cherry 
pick request for 3.4.0.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20818] 3.4 cherry pick: 5fa3f6d82d61 and a8470f88e7b4 - OS X installer use SQLite 3.8.3.1

[Ned Deily]

New submission from Ned Deily:

Update the OS X installer build to use SQLite 3.8.3.1 instead of 3.8.3 (see 
Issue20465).

--
assignee: larry
components: Build
messages: 212524
nosy: larry, ned.deily
priority: release blocker
severity: normal
stage: commit review
status: open
title: 3.4 cherry pick: 5fa3f6d82d61 and a8470f88e7b4 - OS X installer use 
SQLite 3.8.3.1
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20465] Upgrade SQLite to 3.8.3 with 3.4.0 Windows and OS X installers

[Roundup Robot]

Roundup Robot added the comment:

New changeset a8470f88e7b4 by Ned Deily in branch 'default':
Issue #20465: fix NEWS typo (it's 3.8.3.1)
http://hg.python.org/cpython/rev/a8470f88e7b4

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20465] Upgrade SQLite to 3.8.3 with 3.4.0 Windows and OS X installers

[Roundup Robot]

Roundup Robot added the comment:

New changeset 5fa3f6d82d61 by Ned Deily in branch 'default':
Issue #20465: Update OS X installer build to use SQLite 3.8.0.1.
http://hg.python.org/cpython/rev/5fa3f6d82d61

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Stefan Krah]

Stefan Krah added the comment:

aubmoon: Would it be a possibility just to use 'f' instead?

>>> "{:+10.7f}".format(1.12345678)
'+1.1234568'
>>> "{:+10.7f}".format(0.12345678)
'+0.1234568'

--
nosy: +skrah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20731] Python 3.3.4: SyntaxError with correct source code encoding # -*- coding: latin-1 -*-

[Martin v . Löwis]

Martin v. Löwis added the comment:

Thanks for fixing it.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[aubmoon]

aubmoon added the comment:

Neither of those strictly meets the stated format. '0.12345678' is missing
the + which is explicit in the format and '+0.1234567' does not have 8
decimal places. Only '+.12345678' has a length of 10, 8 decimal places, and
the required sign. I realize this definitely an edge case, but it was
encountered in real life.

Thanks again for the careful consideration of this issue.

-Mark

On Saturday, March 1, 2014, Mark Lawrence  wrote:

>
> Mark Lawrence added the comment:
>
> '0.12345678' or '+0.1234567' could both be considered equally valid.  Who
> can say which is really The One True Way? :)
>
> --
> nosy: +BreamoreBoy
>
> ___
> Python tracker >
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20816] inspect.getcallargs() attempts to iterate over None

[Yury Selivanov]

Changes by Yury Selivanov :


--
assignee:  -> yselivanov
nosy: +ncoghlan

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20817] inspect.getcallargs() raises the wrong error if 3+ arguments are missing

[Yury Selivanov]

Changes by Yury Selivanov :


--
assignee:  -> yselivanov
nosy: +larry, ncoghlan, yselivanov

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1043134] Add preferred extensions for MIME types

[David Lindquist]

David Lindquist added the comment:

I don't think it is unreasonable to return a well-known extension for certain 
mime types, text/plain being the most obvious (and most in need of repair; 
.ksh??).

I've attached a patch based on the previous discussion.

--
keywords: +patch
nosy: +david.lindquist
Added file: http://bugs.python.org/file34262/mimetypes.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17457] Unittest discover fails with namespace packages and builtin modules

[Roundup Robot]

Roundup Robot added the comment:

New changeset 57cb8a6e8f10 by R David Murray in branch 'default':
whatsnew: unittest discover works on namespace packages (#17457).
http://hg.python.org/cpython/rev/57cb8a6e8f10

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20815] ipaddress unit tests PEP8

[Michel Albert]

Michel Albert added the comment:

Thanks for the quick reply!

I did not know the pep8 tool added it's own rules :( I have read PEP8 a long 
while ago and have since relied on the tool to do "the right thing". Many of 
it's idiosyncrasies have probably made their way into my blood since :(

And you're right: The PEP is actually explicitly saying that it's okay to leave 
out the white-space to make operator precedence more visible (for reference: 
http://legacy.python.org/dev/peps/pep-0008/#other-recommendations).

I will undo those changes.

Is there anything else that immediately caught your eye so I can address it in 
the update?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20817] inspect.getcallargs() raises the wrong error if 3+ arguments are missing

[Jeremiah Lowin]

Jeremiah Lowin added the comment:

The bug is caused by a list of names not getting properly expanded when 
generating the error message. This patch fixes it (simply by adding a * in the 
appropriate place) and tests that a TypeError, not an IndexError, is raised.

--
keywords: +patch
Added file: http://bugs.python.org/file34261/issue20817.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20817] inspect.getcallargs() raises the wrong error if 3+ arguments are missing

[Jeremiah Lowin]

New submission from Jeremiah Lowin:

If inspect.getcallargs() is called on a function and three or more arguments 
are missing, an IndexError is raised instead of the expected TypeError.

This bug is present in Python 3.3 and 3.4.0 rc1 (5e05d7d3db9c). However, it 
worked as expected in Python 2.7.6.

Example:

>>> import inspect
>>> def fn(a, b, c):
>>> pass
>>> inspect.getcallargs(fn)

Result: 
IndexError: tuple index out of range
Expected:
TypeError: fn() missing 3 required positional arguments: 'a', 'b' and 'c'

--
components: Library (Lib)
messages: 212514
nosy: jlowin
priority: normal
severity: normal
status: open
title: inspect.getcallargs() raises the wrong error if 3+ arguments are missing
type: behavior
versions: Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20816] inspect.getcallargs() attempts to iterate over None

[Jeremiah Lowin]

Jeremiah Lowin added the comment:

Apologies, the patch is attached here.

--
keywords: +patch
Added file: http://bugs.python.org/file34260/issue20816.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20816] inspect.getcallargs() attempts to iterate over None

[Jeremiah Lowin]

Jeremiah Lowin added the comment:

I created a patch to resolve this. 

If a function has keyword-only arguments, then inspect.getcallargs checks if 
the argument is in kwonlydefaults. However, kwonlydefaults is None if no 
defaults were specified. In that situation, 'kwarg in kwonlydefaults' raises 
the TypeError.

The quick fix is simply to test kwonlydefaults before testing if kwarg is in it.

The test for this situation is a little verbose because a TypeError is expected 
and one is raised, just the wrong one, so I parse the error message.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20746] test_pdb fails in refleak mode

[Xavier de Gaye]

Xavier de Gaye added the comment:

See also issue 20766.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20766] reference leaks in pdb

[Xavier de Gaye]

Xavier de Gaye added the comment:

After applying patch 'regrtest.diff' from issue 20746, the command:

  $ ./python -m test -W -R3:3 test_pdb

succeeds now and shows there are no reference leaks.


However, with the following change in Lib/test/test_pdb.py and patch 
'regrtest.diff' applied:

diff --git a/Lib/test/test_pdb.py b/Lib/test/test_pdb.py
--- a/Lib/test/test_pdb.py
+++ b/Lib/test/test_pdb.py
@@ -34,7 +34,7 @@
 """This tests the custom displayhook for pdb.
 
 >>> def test_function(foo, bar):
-... import pdb; pdb.Pdb(nosigint=True).set_trace()
+... import pdb; pdb.Pdb().set_trace()
 ... pass
 
 >>> with PdbTestInput([


there are reference leaks:

$ ./python -m test -R 3:3 test_pdb
[1/1] test_pdb
beginning 6 repetitions
123456
..
test_pdb leaked [200, 200, 200] references, sum=600
test_pdb leaked [43, 43, 43] memory blocks, sum=129
1 test failed:
test_pdb


And now with the proposed patch in the previous msg 212171 'refleak.patch' of 
this issue that fixes the sigint_handler leak, and also patch 'regrtest.diff' 
applied:

$ ./python -m test -R 3:3 test_pdb
[1/1] test_pdb
beginning 6 repetitions
123456
..
1 test OK.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20816] inspect.getcallargs() attempts to iterate over None

[Brett Cannon]

Changes by Brett Cannon :


--
nosy: +yselivanov

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20816] inspect.getcallargs() attempts to iterate over None

[Jeremiah Lowin]

New submission from Jeremiah Lowin:

Tested in Python 3.3 and Python 3.4.0rc1 5e05d7d3db9c

If a function has keyword-only arguments but no keyword-only defaults, then 
calling inspect.getcallargs with no arguments results in the wrong TypeError 
being raised.

Example:

>>> import inspect
>>> def fn(*, a): 
>>>pass
>>> inspect.getcallargs(fn)

Result: 
TypeError: argument of type 'NoneType' is not iterable

Expected Result: 
TypeError: fn() missing 1 required keyword-only argument: 'a'

--
components: Library (Lib)
messages: 212509
nosy: jlowin
priority: normal
severity: normal
status: open
title: inspect.getcallargs() attempts to iterate over None
type: behavior
versions: Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20812] Explicitly cover application migration in the 2->3 guide

[Brett Cannon]

Brett Cannon added the comment:

Something like this should go at the top almost as a tl;dr to get the point 
across that regardless of the state of your dependencies, start writing Python 
3-compatible code **today** and if you must update old code piecemeal. I'll add 
something next time I have time (should be Friday).

--
assignee:  -> brett.cannon

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20813] Backport revised 2to3 guide to older branches

[Brett Cannon]

Brett Cannon added the comment:

But then if Larry doesn't cherrypick it then backporting would be a good idea, 
and considering it's probably safer to just backport the changes by doing a 
whole copy copy then we might as well backport.

--
assignee:  -> brett.cannon

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20813] Backport revised 2to3 guide to older branches

[Brett Cannon]

Brett Cannon added the comment:

Good point about the 2.7 backport. I'm still not worried about 3.3, though, by 
the fact that 3.4 should land in less than a month.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20731] Python 3.3.4: SyntaxError with correct source code encoding # -*- coding: latin-1 -*-

[Roundup Robot]

Roundup Robot added the comment:

New changeset dcf4fbf446ca by Benjamin Peterson in branch '3.3':
fix test on debug builds (closes #20731)
http://hg.python.org/cpython/rev/dcf4fbf446ca

--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20731] Python 3.3.4: SyntaxError with correct source code encoding # -*- coding: latin-1 -*-

[Georg Brandl]

Georg Brandl added the comment:

This needs to be fixed for 3.3.5rc2.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20746] test_pdb fails in refleak mode

[Xavier de Gaye]

Xavier de Gaye added the comment:

The doctests are executed with 'test.globs' as globals which is set in the 
'find' method of doctest.DocTestFinder, and cleared after each run (unless 
'clear_globs' is false).  One possible fix is to have test.regrtest 'find' a 
new test_runner before each run instead of always using the same one. This is 
what does the attached patch.

--
keywords: +patch
nosy: +xdegaye
Added file: http://bugs.python.org/file34259/regrtest.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Mark Lawrence]

Mark Lawrence added the comment:

'0.12345678' or '+0.1234567' could both be considered equally valid.  Who can 
say which is really The One True Way? :)

--
nosy: +BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11558] Raise a more helpful exception in email.message.Message.attach after set_payload("some string")

[R. David Murray]

R. David Murray added the comment:

Thanks, Varun.  Your patch addresses an issue with the current API, but it 
doesn't address the problem raised in this issue.  The problem in this issue is 
what happens when the *payload* is a string, and you call attach (to attach a 
message object) on that message.

Your fix addresses what happens if you pass a string to attach itself.  This 
also results in an invalid message (it ends up with a payload that contains a 
list consisting of a single string).  Thinking about changing this raises some 
interesting questions, though.  For one, the problem isn't that the argument to 
attach was a string, but that it was not an object that generator knows how to 
handle (that is, it wasn't a Message object).  For another, is it possible 
someone is using the email package in a weird context where attaching 
non-message objects is actually useful?  If so, and we disallow it, then we 
break someones code.

Since no one has reported calling attach with a non-message object as an actual 
bug, I'm inclined not to make this change.  Python is a "consenting adults" 
language, so unless there is a specific reason to disallow something, we 
generally allow it.

To work on a fix for the reported issue, you should start by turning the code 
in test_email_attach_to_string into a unit test.

--
components: +email
nosy: +barry

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20374] Failure to compile with readline-6.3-rc1

[koobs]

Changes by koobs :


--
nosy: +koobs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20815] ipaddress unit tests PEP8

[Nick Coghlan]

Nick Coghlan added the comment:

Unfortunately, the pep8 tool includes some additional invented rules of its 
own, mostly related to being far too strict about indentation of continuation 
lines.

PEP 8 is actually mostly silent on that topic, merely pointing out a couple of 
specific things *not* to do. It's the tool that extrapolates a whole host of 
continuation line indentation rules that even PEP 8 itself doesn't meet.

There's also no blanket requirement in the PEP to have spaces around all binary 
operators (since that doesn't always aid readability), just a limited subset of 
them.

I've recently filed a bug against the tool itself, suggesting that given its 
name, its default behaviour should be limited to things that are actually 
backed up by the PEP.

That said, I think some of the cases picked up here do represent genuine 
readability improvements due to improved alignment. They just need to be 
separated out from the spurious changes resulting from invented rules in the 
pep8 tool.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16135] Removal of OS/2 support

[Roundup Robot]

Roundup Robot added the comment:

New changeset 5e05d7d3db9c by Andrew Kuchling in branch 'default':
#16135: remove mentions of OS/2 from the documentation
http://hg.python.org/cpython/rev/5e05d7d3db9c

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11558] Raise a more helpful exception in email.message.Message.attach after set_payload("some string")

[Varun Sharma]

Varun Sharma added the comment:

I have made a patch which raises TypeError whenever a string type payload is 
attached to message using email.Message.attach() method.I have also added a 
unit test for the same. Need review.

--
keywords: +patch
nosy: +varun
Added file: http://bugs.python.org/file34258/string_payload_to_attach.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20815] ipaddress unit tests PEP8

[Michel Albert]

New submission from Michel Albert:

While I was looking at the source of the ipaddress unit-tests, I noticed a 
couple of PEP8 violations. This patch fixes these (verified using the ``pep8`` 
tool).

There are no behavioural changes. Only white-space.

Test-cases ran successfully before, and after the change was made.

--
components: Tests
files: test_ipaddress_pep8.patch
keywords: patch
messages: 212497
nosy: exhuma, ncoghlan, pmoody
priority: normal
severity: normal
status: open
title: ipaddress unit tests PEP8
versions: Python 3.5
Added file: http://bugs.python.org/file34257/test_ipaddress_pep8.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20465] Upgrade SQLite to 3.8.3 with 3.4.0 Windows and OS X installers

[Martin v . Löwis]

Martin v. Löwis added the comment:

3.8.3 has been superseded by 3.8.3.1.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Eric V. Smith]

Eric V. Smith added the comment:

Oops, not sure how the nosy list got changed. Sorry about that.

--
nosy:  -anthonybaxter, barry, benjamin.peterson, eric.araujo, georg.brandl, 
gvanrossum, lemburg, loewis, tarek

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Eric V. Smith]

Eric V. Smith added the comment:

I think you always want the leading zero. Mark (Dickinson), what do yo think?

And I also think changing it at this point would be problematic.

--
nosy: +anthonybaxter, barry, benjamin.peterson, eric.araujo, georg.brandl, 
gvanrossum, lemburg, loewis, tarek

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20731] Python 3.3.4: SyntaxError with correct source code encoding # -*- coding: latin-1 -*-

[Arfrever Frehtes Taifersar Arahesis]

Changes by Arfrever Frehtes Taifersar Arahesis :


--
resolution: fixed -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20633] SystemError: Parent module 'multiprocessing' not loaded, cannot perform relative import

[Richard Oudkerk]

Changes by Richard Oudkerk :


--
assignee:  -> sbt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20814] tracemalloc example - Pretty Top

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +haypo
versions:  -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20811] str.format for fixed width float can return a string longer than the maximum specified

[Mark Dickinson]

Changes by Mark Dickinson :


--
nosy: +mark.dickinson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20814] tracemalloc example - Pretty Top

[Jeong-Min Lee]

Changes by Jeong-Min Lee :


--
title: tracemalloc example -> tracemalloc example - Pretty Top

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20814] tracemalloc example

[Jeong-Min Lee]

New submission from Jeong-Min Lee:

Running the Pretty top example 
(http://docs.python.org/dev/library/tracemalloc.html#pretty-top) in the 
tracemalloc module documentation causes a ValueError.


Traceback (most recent call last):
  File "t.py", line 32, in 
display_top(snapshot, 10)
  File "t.py", line 9, in display_top
top_stats = snapshot.statistics(group_by)
  File "/home/falsetru/h/cpython/Lib/tracemalloc.py", line 449, in 
statistics
grouped = self._group_by(key_type, cumulative)
  File "/home/falsetru/h/cpython/Lib/tracemalloc.py", line 395, in _group_by
raise ValueError("unknown key_type: %r" % (key_type,))
ValueError: unknown key_type: 10

The last line of the example should be:

display_top(snapshot, limit=10)

or:

display_top(snapshop)

--
assignee: docs@python
components: Documentation
messages: 212493
nosy: Jeong-Min.Lee, docs@python
priority: normal
severity: normal
status: open
title: tracemalloc example
versions: Python 3.4, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19966] Wrong mtimes of Include/Python-ast.h and Python/Python-ast.c in tarballs

[koobs]

Changes by koobs :


--
nosy: +koobs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20731] Python 3.3.4: SyntaxError with correct source code encoding # -*- coding: latin-1 -*-

[koobs]

koobs added the comment:

Regressions on FreeBSD buildbots (test_coding)

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.0%203.3/builds/626/steps/test/logs/stdio

--
nosy: +koobs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com