[issue10183] test_concurrent_futures failure on Windows

[Brian Quinlan]

Brian Quinlan  added the comment:

Would you include the entire output of the test run?

--

___
Python tracker 

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

[issue4113] Add custom __repr__ to functools.partial

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> Looks like a reasonable proposal, but coding this in C is a chore. 

It's not that bad.  Most C code is a bit of a chore compared to Python but it 
really doesn't take much to write a C equivalent of: "functools.partial(%r, 
%s)" % (self.func, ', '.join(repr(a) for a in self.args)

>  How hard/inefficient would it be to have 99% of partial 
> coded in C and one stub in functools.py?

Let's not do this.  There is too little benefit to warrant going down the path 
of splitting the code across two langauges.

--

___
Python tracker 

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

[issue10183] test_concurrent_futures failure on Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Y:\>py3k\__svn__\PCbuild\amd64\python_d.exe -m test.regrtest -v 
test_concurrent_futures
== CPython 3.2a4+ (py3k, Nov 18 2010, 11:12:09) [MSC v.1500 64 bit (AMD64)]
==   Windows-7-6.1.7600 little-endian
==   Y:\py3k\__svn__\build\test_python_2016
[1/1] test_concurrent_futures
test_map (test.test_concurrent_futures.ProcessPoolExecutorTest) ... ok
test_map_exception (test.test_concurrent_futures.ProcessPoolExecutorTest) ... ok

test_map_timeout (test.test_concurrent_futures.ProcessPoolExecutorTest) ... FAIL

test_submit (test.test_concurrent_futures.ProcessPoolExecutorTest) ... ok
test_submit_keyword (test.test_concurrent_futures.ProcessPoolExecutorTest) ... o
k
test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... ok
test_map_exception (test.test_concurrent_futures.ThreadPoolExecutorTest) ... ok
test_map_timeout (test.test_concurrent_futures.ThreadPoolExecutorTest) ... ok
test_submit (test.test_concurrent_futures.ThreadPoolExecutorTest) ... ok
test_submit_keyword (test.test_concurrent_futures.ThreadPoolExecutorTest) ... ok

test_all_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... ok
test_all_completed_some_already_completed (test.test_concurrent_futures.ProcessP
oolWaitTests) ... ok
test_first_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... ok
test_first_completed_one_already_completed (test.test_concurrent_futures.Process
PoolWaitTests) ... ok
test_first_exception (test.test_concurrent_futures.ProcessPoolWaitTests) ... ok
test_first_exception_one_already_failed (test.test_concurrent_futures.ProcessPoo
lWaitTests) ... ok
test_first_exception_some_already_complete (test.test_concurrent_futures.Process
PoolWaitTests) ... ok
test_timeout (test.test_concurrent_futures.ProcessPoolWaitTests) ... FAIL
test_all_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_all_completed_some_already_completed (test.test_concurrent_futures.ThreadPo
olWaitTests) ... ok
test_first_completed (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_first_completed_one_already_completed (test.test_concurrent_futures.ThreadP
oolWaitTests) ... ok
test_first_exception (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_first_exception_one_already_failed (test.test_concurrent_futures.ThreadPool
WaitTests) ... ok
test_first_exception_some_already_complete (test.test_concurrent_futures.ThreadP
oolWaitTests) ... ok
test_timeout (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_no_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) ... o
k
test_zero_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) ...
 ok
test_no_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTests) ... ok

test_zero_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTests) ...
ok
test_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_cancelled (test.test_concurrent_futures.FutureTests) ... ok
test_done (test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_already_cancelled (test.test_concurrent_futures.FutureTests)
... ok
test_done_callback_already_failed (test.test_concurrent_futures.FutureTests) ...
 ok
test_done_callback_already_successful (test.test_concurrent_futures.FutureTests)
 ... ok
test_done_callback_raises (test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_with_cancel (test.test_concurrent_futures.FutureTests) ... ok

test_done_callback_with_exception (test.test_concurrent_futures.FutureTests) ...
 ok
test_done_callback_with_result (test.test_concurrent_futures.FutureTests) ... ok

test_exception_with_success (test.test_concurrent_futures.FutureTests) ... ok
test_exception_with_timeout (test.test_concurrent_futures.FutureTests) ... ok
test_repr (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_success (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_timeout (test.test_concurrent_futures.FutureTests) ... ok
test_running (test.test_concurrent_futures.FutureTests) ... ok
test_context_manager_shutdown (test.test_concurrent_futures.ProcessPoolShutdownT
est) ... ok
test_del_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... ok
test_processes_terminate (test.test_concurrent_futures.ProcessPoolShutdownTest)
... ok
test_run_after_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) .
.. ok
test_context_manager_shutdown (test.test_concurrent_futures.ThreadPoolShutdownTe
st) ... ok
test_del_shutdown (test.test_concurrent_futures.ThreadPoolShutdownTest) ... ok
test_run_after_shutdown (test.test_concurrent_futures.ThreadPoolShutdownTest) ..
. ok
test_threads_terminate (test.test_concurrent_futures.ThreadPoolShutdownTest) ...
 ok

==
FAIL: test_map_timeout (test.test_concurrent_futures.ProcessPoolExecutorTest)

[issue10351] Add autocompletion for keys in dictionaries

[Valery Khamenya]

Valery Khamenya  added the comment:

Guys, do you expect anythig else from me in respect to this issue? Let me know 
it before my non-stopable garbage collector wipes all the details from my brain 
away :)

--

___
Python tracker 

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

[issue10351] Add autocompletion for keys in dictionaries

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +facundobatista, georg.brandl

___
Python tracker 

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

[issue7652] Merge C version of decimal into py3k.

[Stefan Krah]

Stefan Krah  added the comment:

An update on the progress:

All development currently happens in my private mpdecimal repository. The
next version of mpdecimal (2.0) is finished, stable and will be released
once all tests have completed successfully. Running the whole test suite
can take several weeks, since Valgrind is involved and all Python versions
from 2.5 to 3.2 are tested.


In py3k-cdecimal, r86497 is an exact copy of mpdecimal-2.0. All buildbots
pass the short tests.


Major improvements:

   o Full compatibility with decimal.py 3.2, including the new hash
 functions and float operations.

   o With the new FloatOperation signal, accidental float operations
 can be detected.

   o The underlying library - libmpdec - now has 100% code coverage
 together with Makefile targets for creating coverage reports.
 In particular, every possible allocation failure during an
 operation can be tested in brute force style.

   o The module has 85% code coverage. All lines except failures
 of Python C-API functions are tested.

   o Several minor bug fixes, most of them deal with allocation
 failures under extreme bignum conditions.



Potential reviewers:

I'll be happy to answer questions here or privately. IMO the best way to
get acquainted with the module is to do the regular build and tests first,
then explore Lib/test/mpdecimal, reading LIBTEST.txt and PYTEST.txt.

--

___
Python tracker 

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

[issue10452] Unhelpful diagnostic 'cannot find the path specified'

[Raphael Mankin]

New submission from Raphael Mankin :

Something somewhere in the library issues the diagnostic 'The system cannot 
find the path specified' with no indication of what path it was looking for nor 
where the error was detected.

The relevant routine needs modification to print at least the path and 
preferably also a back-trace.

--
components: Library (Lib)
messages: 121453
nosy: r...@mankin.org.uk
priority: normal
severity: normal
status: open
title: Unhelpful diagnostic 'cannot find the path specified'
versions: Python 2.6

___
Python tracker 

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

[issue10260] Add a threading.Condition.wait_for() method

[Kristján Valur Jónsson]

Kristján Valur Jónsson  added the comment:

Committed as revision 86510

--
resolution:  -> accepted
status: open -> closed

___
Python tracker 

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

[issue10452] Unhelpful diagnostic 'cannot find the path specified'

[Eric Smith]

Eric Smith  added the comment:

What code were you executing when this message was printed? What platform are 
you running on? What's the exact version of Python this happens with? (If 
you're running 2.6.x, what's "x" equal to?)

--
nosy: +eric.smith

___
Python tracker 

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

[issue10444] A mechanism is needed to override waiting for Python threads to finish

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo
versions:  -Python 2.6, Python 2.7, Python 3.1, Python 3.3

___
Python tracker 

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

[issue10452] Unhelpful diagnostic 'cannot find the path specified'

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo

___
Python tracker 

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

[issue10451] memoryview can be used to write into readonly buffer

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +pitrou

___
Python tracker 

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

[issue10452] Unhelpful diagnostic 'cannot find the path specified'

[Eric Smith]

Eric Smith  added the comment:

I ask about the specific version and platform because the string "cannot find 
the path specified" doesn't appear anywhere in release26-maint. And indeed 
"cannot find the" doesn't appear anywhere except comments. I'm going to close 
this issue, assuming it's a problem in something other than the standard 
library. If you have a repeatable case, please let us know and reopen the issue 
(or I can reopen it for you).

--
resolution:  -> invalid
stage:  -> committed/rejected
status: open -> closed
type:  -> behavior

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Mark Dickinson]

Mark Dickinson  added the comment:

I wouldn't risk changing the exception type in 2.7.  It's fine for 3.2.

--

___
Python tracker 

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

[issue9991] xmlrpc client ssl check faulty

[Senthil Kumaran]

Senthil Kumaran  added the comment:

Fixed in r86514 (py3k) and r86515 (release31-maint).

--
assignee:  -> orsenthil
resolution:  -> fixed
stage:  -> committed/rejected

___
Python tracker 

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

[issue10452] Unhelpful diagnostic 'cannot find the path specified'

[Tim Golden]

Tim Golden  added the comment:

It's almost certainly coming straight back from the O/S,
where Python is doing its usual thing of channelling
an O/S error directly. Obviously we could special-case
this or any other specific error; but we usually don't

--
nosy: +tim.golden

___
Python tracker 

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

[issue9991] xmlrpc client ssl check faulty

[Senthil Kumaran]

Changes by Senthil Kumaran :


--
status: open -> closed

___
Python tracker 

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

[issue10447] zipfile: IOError for long directory paths on Windows

[R. David Murray]

R. David Murray  added the comment:

I agree with Amaury.  IMO the IOError is the correct error, since it is 
bubbling up unexpectedly (from zipfile's viewpoint) from a lower layer and is 
not an error specific to the zip protocol implementation. (CF the discussion 
surrounding PEP 3151).

Probably there should indeed be a common base class for the existing zipfile 
errors, but that's a feature request.

--
nosy: +r.david.murray
stage:  -> committed/rejected
status: pending -> closed

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Stefan Krah]

Stefan Krah  added the comment:

Thanks for all the comments! I agree that a change in 2.7 might cause
trouble. 

Committed the ValueError in r86517 (py3k).

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

___
Python tracker 

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

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

[Martin v . Löwis]

Martin v. Löwis  added the comment:

In case it isn't clear from the discussion in issue8792: I'd be in favor of 
supporting extensions as long as their usage is an opt-in feature. The current 
nil support is already an opt-in feature. If alternative spellings of nil need 
to be supported, or other extensions, it might be necessary to refactor this 
extension support a bit, so that extensions can be independently be developed 
and activated.

As for Python's usage of nil: it is specified in

http://ontosys.com/xml-rpc/extensions.php

and also referenced in the Wikipedia. IMO, it would have been better if Apache 
had used the pre-existing extension, instead of coming up with its own 
(supposedly only because the pre-existing one wasn't namespace-based).

--

___
Python tracker 

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

[issue8792] Support Apache extensions to XML-RPC in xmlrpclib

[Martin v . Löwis]

Martin v. Löwis  added the comment:

> An addition: It was reported in #10425 that None values are
> incorrectly serialized as , instead of just
> , or maybe <{namespace prefix for extensions defined by
> Apache}:nil/>.

This is not incorrect, but follows the specification of the nil
element, see, for example

http://en.wikipedia.org/wiki/XML-RPC

--

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[Martin v . Löwis]

Martin v. Löwis  added the comment:

db: there *is* no "sane system ca path", or Python would have done that long 
ago. On Windows, it may be possible to drop OpenSSL, and use the system 
certificate store. However, that would be a major rewrite, and it may not be 
possible to provide the entire API anymore.

The best that could be done is to provide a configuration option (e.g. global 
variable) that should be treated as a default value, and then leave it to 
people distributing Python to fill out this variable in a sensible way.

--
nosy: +loewis

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> The best that could be done is to provide a configuration option (e.g.
> global variable) that should be treated as a default value, and then
> leave it to people distributing Python to fill out this variable in a
> sensible way.

Actually, OpenSSL already does a similar thing (see issue10443).

--

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

The changes added in r82301 are misleading because code examples in this HOWTO 
have been converted to 3.x.  I am attaching a patch that removes "has not yet 
been updated to cover the 3.x" warning and makes some minor stylistic changes.

I have bumped the release version to 1.12, but I would like to remove the 
revision history which is largely irrelevant.

--
keywords: +patch
Added file: http://bugs.python.org/file19631/issue4153.diff

___
Python tracker 

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

[issue4476] compileall.py fails if current dir has a "types" subdir with 3.0 (ok with 2.5)

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo
versions: +Python 3.1, Python 3.2 -Python 3.0

___
Python tracker 

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

[issue10453] Add -h/--help option to compileall

[Éric Araujo]

New submission from Éric Araujo :

It would be useful if “python -m compileall -h” was possible.  Right now it 
fails with “option -h not recognized” and prints its help text, which is a bit 
silly :)

Bug week-end candidate!

--
assignee: eric.araujo
components: Library (Lib)
keywords: easy
messages: 121467
nosy: eric.araujo
priority: normal
severity: normal
stage: needs patch
status: open
title: Add -h/--help option to compileall
type: feature request
versions: Python 3.2

___
Python tracker 

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

[issue10450] Fix markup in Misc/NEWS

[Dave Malcolm]

Dave Malcolm  added the comment:

Perhaps "make patchcheck" (a.k.a Tools/scripts/patchcheck.py ) should verify 
the markup of Misc/NEWS?  Not sure what the easiest way to do that is, though, 
without bringing in lots of deps.

--
nosy: +dmalcolm

___
Python tracker 

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

[issue10454] Clarify compileall options

[Éric Araujo]

New submission from Éric Araujo :

This is the help text of compileall:

 usage: python compileall.py [-l] [-f] [-q] [-d destdir] [-x regexp] [-i list] 
[directory|file ...]
 -l: don't recurse down
 -f: force rebuild even if timestamps are up-to-date
 -q: quiet operation
 -d destdir: purported directory name for error messages
if no directory arguments, -l sys.path is assumed
 -x regexp: skip files matching the regular expression regexp
the regexp is searched for in the full path of the file
 -i list: expand list with its content (file and directory names)
 -b: Produce legacy byte-compile file paths

1) I do not understand the help of -d and -i.  Experimenting with the script, 
reading the code and eventually looking at the file history would certainly 
clear that.

2) The short usage line at the top also lacks mention of “-b”.

3) (minor) I want to rephrase -x, -d and -b.

Bug week-end candidate!

--
assignee: d...@python
components: Documentation
keywords: easy
messages: 121469
nosy: d...@python, eric.araujo
priority: normal
severity: normal
stage: needs patch
status: open
title: Clarify compileall options
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

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

[issue10454] Clarify compileall command-line options

[Éric Araujo]

Changes by Éric Araujo :


--
title: Clarify compileall options -> Clarify compileall command-line options

___
Python tracker 

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

[issue10453] Add -h/--help option to compileall

[Éric Araujo]

Éric Araujo  added the comment:

One neat way to solve this is to make compileall use argparse.

--

___
Python tracker 

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

[issue1353344] python.desktop

[Dave Malcolm]

Changes by Dave Malcolm :


--
nosy: +dmalcolm

___
Python tracker 

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

[issue10454] Clarify compileall command-line options

[Éric Araujo]

Éric Araujo  added the comment:

In addition, the line “if no directory arguments, -l sys.path is assumed” seems 
misplaced.

--

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[Martin v . Löwis]

Martin v. Löwis  added the comment:

>> The best that could be done is to provide a configuration option (e.g.
>> global variable) that should be treated as a default value, and then
>> leave it to people distributing Python to fill out this variable in a
>> sensible way.
> 
> Actually, OpenSSL already does a similar thing (see issue10443).

This may not be satisfying to users. For example, our Windows
distribution doesn't ship with any certicates (AFAIK); I have no
clue where exactly OpenSSL would be looking for them, either.
People worried about this problem probably would want a way to
fill the list of trusted CA certificates.

Regards,
Martin

--
title: some stdlib modules need to be updated to handle SSL certificate 
validation -> some stdlib modules need to be updated to handle SSL  
certificate validation

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[david]

david  added the comment:

On 19 November 2010 03:18, Martin v. Löwis  wrote:
>
> Martin v. Löwis  added the comment:
>
>>> The best that could be done is to provide a configuration option (e.g.
>>> global variable) that should be treated as a default value, and then
>>> leave it to people distributing Python to fill out this variable in a
>>> sensible way.
>>
>> Actually, OpenSSL already does a similar thing (see issue10443).
>
> This may not be satisfying to users. For example, our Windows
> distribution doesn't ship with any certicates (AFAIK); I have no
> clue where exactly OpenSSL would be looking for them, either.
> People worried about this problem probably would want a way to
> fill the list of trusted CA certificates.
>

Martin does it matter?
To be honest I don't know about that many client side python windows
applications for which this is a problem for. Maybe I am mistaken. If
this is the case, then how do these projects work at the moment? (or
do they just not care about this...) . However, they could bundle
their own certificates, so I don't see this as an issue.

However, you seem confused here:
" I have no
> clue where exactly OpenSSL would be looking for them, either.
> People worried about this problem probably would want a way to
> fill the list of trusted CA certificates."

Erh, those people can already do this, but the problem is by default
none are selected.
IMHO something is probably better than nothing in this case(by default).

--
title: some stdlib modules need to be updated to handle SSL certificate 
validation -> some stdlib modules need to be updated to handle SSL certificate 
validation

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


Added file: http://bugs.python.org/file19632/issue4153.diff

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


Removed file: http://bugs.python.org/file19631/issue4153.diff

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

r82301 appears to be a blind merge of r82120 from the trunk.  It is fairly 
obvious that it was not intentional.

--

___
Python tracker 

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

[issue9312] Fix usage of :option: markup in stdlib ReST docs

[Éric Araujo]

Éric Araujo  added the comment:

Patch tweaked and committed in r86521.  Gory details follow.

The patch applied with only two fuzzy hunks and one rejected hunk.

I did a careful review of "" → ``""`` changes and edited a number of them.  I’m 
confident in my choices but am of course open to comments on the checkin.

My remark about not using :program:`name --option` was wrong.  It is actually 
supported, see for instance in shutil.rst “Unix command :program:`cp -p`”.  I 
apologize for causing you unnecessary work.  I changed that back before 
committing.

I ran “make clean html” in the docs (no warnings) and looked at the HTML output 
for each change.  Modules that wrongly used :option: are fixed; conversely, 
timeit and unittest now have a good-looking, indexed list of options, the 
program/cmdoption combo you used is terrific!

Actually, I found that so cool that I added an option list for “unittest 
discover” (was a table) and “compileall” (was a plain paragraph, missing two 
options).  Consider that an experiment; I’m willing to revert them if people 
prefer the old form.

I’ll rewrap too long or too short lines in a following commit.  I’ll also 
backport relevant parts to 3.1 and 2.7 with the approval of the release manager.

Thank you Eli for this contribution.  Thanks Terry and Georg for the help.

--
resolution: accepted -> fixed
stage: commit review -> committed/rejected
status: pending -> open

___
Python tracker 

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

[issue2244] urllib and urllib2 decode userinfo multiple times

[Senthil Kumaran]

Senthil Kumaran  added the comment:

Fixed in r86520 (py3k) and r86522 (release31-maint). 
unquote happens at the first level inside Request class, _parse method.

Shall port to py2.7.

--
nosy:  -BreamoreBoy
resolution:  -> fixed
stage: patch review -> committed/rejected

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
nosy: +akuchling

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> > This may not be satisfying to users. For example, our Windows
> > distribution doesn't ship with any certicates (AFAIK); I have no
> > clue where exactly OpenSSL would be looking for them, either.
> > People worried about this problem probably would want a way to
> > fill the list of trusted CA certificates.

Right, this is just a helper in case OpenSSL is configured correctly by
the OS vendor (the OpenSSL packaged by Linux distros usually is).

> Erh, those people can already do this, but the problem is by default
> none are selected.
> IMHO something is probably better than nothing in this case(by default).

We can't change anything *by default* since it would break
compatibility. We can just provide helpers and arguments to make it easy
to switch to a more "secure" behaviour (for some meaning of secure).

--

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo

___
Python tracker 

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

[issue1669349] make install fails if no previous Python installation

[lkraav]

lkraav  added the comment:

i think i am running into this trying to cross-compile for 
i686-gentoo-linux-uclibc and have been unable to figure out how to get 
altinstall to succeed:

http://bugs.gentoo.org/show_bug.cgi?id=269111#c12

build log available at 
http://bugs.gentoo.org/attachment.cgi?id=253831&action=view

any thoughts?

--
nosy: +lkraav

___
Python tracker 

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

[issue9991] xmlrpc client ssl check faulty

[Senthil Kumaran]

Senthil Kumaran  added the comment:

r86523(py3k) and r86524(release31-maint)

--

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[david]

david  added the comment:

On 19 November 2010 03:48, Antoine Pitrou  wrote:
>
> Antoine Pitrou  added the comment:
>
>> > This may not be satisfying to users. For example, our Windows
>> > distribution doesn't ship with any certicates (AFAIK); I have no
>> > clue where exactly OpenSSL would be looking for them, either.
>> > People worried about this problem probably would want a way to
>> > fill the list of trusted CA certificates.
>
> Right, this is just a helper in case OpenSSL is configured correctly by
> the OS vendor (the OpenSSL packaged by Linux distros usually is).
>
>> Erh, those people can already do this, but the problem is by default
>> none are selected.
>> IMHO something is probably better than nothing in this case(by default).
>
> We can't change anything *by default* since it would break
> compatibility. We can just provide helpers and arguments to make it easy
> to switch to a more "secure" behaviour (for some meaning of secure).

what about an environmental setting that can be used to enforce
checking (or the like) ?

--

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[Martin v . Löwis]

Martin v. Löwis  added the comment:

>> This may not be satisfying to users. For example, our Windows
>> distribution doesn't ship with any certicates (AFAIK); I have no
>> clue where exactly OpenSSL would be looking for them, either.
>> People worried about this problem probably would want a way to
>> fill the list of trusted CA certificates.
>>
> 
> Martin does it matter?
> To be honest I don't know about that many client side python windows
> applications for which this is a problem for. Maybe I am mistaken.

I can't understand why you are saying that. The very same issues
that people perceive as problems on Unix ("users can be victim
to man in the middle attack") also exist on Windows. If you run
a Python script that does https on Windows, you can *also* be
MITM-victim (as likely as you can on Unix, that is).

Or are you suggesting that Python Windows applications don't use SSL?

> If
> this is the case, then how do these projects work at the moment? (or
> do they just not care about this...) .

"The projects" may be scripts that somebody developed that never get
released. But yes, most people ignore/accept the problem (often as
gruntingly as the Unix users).

> However, they could bundle
> their own certificates, so I don't see this as an issue.

Who is "they"? Most people get their Python binaries from python.org,
and they don't build "applications" from it, but run "scripts".

> However, you seem confused here:
> " I have no
>> clue where exactly OpenSSL would be looking for them, either.
>> People worried about this problem probably would want a way to
>> fill the list of trusted CA certificates."
> 
> Erh, those people can already do this, but the problem is by default
> none are selected.

You misunderstood. I was not proposing that scripts provide a CA
list, but that users might deploy a CA list into their Python
installation, which is then picked up in the same way as you are asking
for on Ubuntu.

--
title: some stdlib modules need to be updated to handle SSL certificate 
validation -> some stdlib modules need to be updated to handle SSL  
certificate validation

___
Python tracker 

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

[issue7828] chr() and ord() documentation for wide characters

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file19633/issue7828.diff

___
Python tracker 

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

[issue7828] chr() and ord() documentation for wide characters

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

Looks good to me, except for a 'stings' near the end of the patch.

--
nosy: +amaury.forgeotdarc

___
Python tracker 

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

[issue1669349] make install fails if no previous Python installation

[lkraav]

lkraav  added the comment:

i have managed to get past unicodedata fails by manually enabling unicodedata 
(https://groups.google.com/group/comp.lang.python/browse_thread/thread/21a3b6db8f5a246b?hl=en).
 got another error right after that, but that might be something further 
gentoo/xcompile specific, details in gentoo bug for those interested.

--

___
Python tracker 

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

[issue7132] Regexp: capturing groups in repetitions

[Matthew Barnett]

Matthew Barnett  added the comment:

Earlier this week I discovered that .Net supports repeated capture and its API 
suggested a much cleaner approach than what Perl offered, so I'll be adding it 
to the regex module at:

http://pypi.python.org/pypi/regex

The new methods will follow the example of .group() & co.

Given a match object m, m.group(i) returns the last match of group i (or None 
if there's no match), so I'll be adding m.captures(i) to return a tuple of the 
captures (an empty tuple if there's no match). I'll also be adding m.starts(i), 
m.ends(i) and m.spans(i).

The issue for this work is #2636.

Units tests are welcome.

--

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Should there be a 'versionchanged' note in the doc, even if the error type was 
not documented?

--

___
Python tracker 

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

[issue7828] chr() and ord() documentation for wide characters

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

Committed in r86526 (3.2) and r86527 (3.1).

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

___
Python tracker 

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

[issue10455] typo in urllib.request documentation

[Jeffrey Finkelstein]

New submission from Jeffrey Finkelstein :

Typo in Doc/library/urllib.request.rst, under the "urllib.response" module 
description: "and" -> "an"

--
assignee: d...@python
components: Documentation
files: urllib.request_typo.diff
keywords: patch
messages: 121487
nosy: d...@python, jfinkels
priority: normal
severity: normal
status: open
title: typo in urllib.request documentation
versions: Python 3.2
Added file: http://bugs.python.org/file19634/urllib.request_typo.diff

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Thanks for persisting with this. Looking at the patch:

@@ -65,7 +63,7 @@
 goal was to have Unicode contain the alphabets for every single human language.
 It turns out that even 16 bits isn't enough to meet that goal, and the modern
 Unicode specification uses a wider range of codes, 0-1,114,111 (0x10 in
-base-16).
+base 16).

I visually parse 0-1,114,111 as 0-1, 114, 111. So I think either the commas 
should be removed or extra spaces are needed: 0-1114111 or 0 - 1,114,111. In 
your recent (and excellent) chr/ord doc patch, you used (or stayed with) 
'hexadecimal' versus 'base 16'. Do we have a standard? I *think* I prefer the 
former.

-character with value 0x12ca (4810 decimal).  The Unicode standard contains a 
lot
+character with value 0x12ca (4,810 decimal).  The Unicode standard contains a 
lot

I prefer without the added comma.

 >>> b'\x80abc'.decode("utf-8", "replace")
-'\ufffdabc'
+'�abc'

Three replacements (i with diaeresis, upside-down ?, 1/2) for one bad char 
looks wrong. With IDLE I get '�abc' (? in hexagon, codepoint 65533). Perhaps 
something just went wrong to patch from your file to my browser window.

@@ -281,10 +279,10 @@
 built-in :func:`ord` function that takes a one-character Unicode string and
 returns the code point value::

You fixed chr/ord doc, need to fix references thereto in this doc.

-point.  The ``\U`` escape sequence is similar, but expects 8 hex digits, not 
4::
+point.  The ``\U`` escape sequence is similar, but expects eight base 16
+digits, not four::

I really think of them as hex or hexadecimal digits, just as 0-9 are decimal, 
not base 10 digits.


 
 >>> s = "a\xac\u1234\u20ac\U8000"
    two-digit hex escape

--

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti

___
Python tracker 

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

[issue10455] typo in urllib.request documentation

[Ezio Melotti]

Ezio Melotti  added the comment:

Fixed in r86528 (py3k) and r86529 (release31-maint), thanks!

--
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

On Thu, Nov 18, 2010 at 2:41 PM, Terry J. Reedy  wrote:
..
> I visually parse 0-1,114,111 as 0-1, 114, 111. So I think either the commas
> should be removed or extra spaces are needed: 0-1114111 or 0 - 1,114,111.

What about "0 through 1,114,111"?

> you used (or stayed with) 'hexadecimal' versus 'base 16'. Do we have a 
> standard?
> I *think* I prefer the former.

I prefer 'base 16'.  I thought about changing 'hexadecimal' to 'base
16' in chr/ord docs, but decided to leave it because the term
'hexadecimal' is used elsewhere on the same page notably in hex()
function description where it is quite appropriate.   No, we don't
have a standard.  I've also seen "base-16" used elsewhere which I
really don't like.

> +    '�abc'
>
> Three replacements (i with diaeresis, upside-down ?, 1/2) for one bad char 
> looks wrong.

That must be UTF-8 misinterpreted as Latin-1.  Won't affect the commit.

> With IDLE I get '�abc' (? in hexagon, codepoint 65533). Perhaps something
> just went wrong to patch from your file to my browser window.

Yes.  I get the same on the terminal window and that's what it should look like.

>  built-in :func:`ord` function that takes a one-character Unicode string and
>  returns the code point value::
>
> You fixed chr/ord doc, need to fix references thereto in this doc.
>

I don't understand.  I think "one-character Unicode string" is fine
here because "Unicode string" means an abstract Unicode string, not
:class:`str`.

> -point.  The ``\U`` escape sequence is similar, but expects 8 hex digits, not 
> 4::
> +point.  The ``\U`` escape sequence is similar, but expects eight base 16
> +digits, not four::
>
> I really think of them as hex or hexadecimal digits, just as 0-9 are decimal, 
> not base 10 digits.
>

I am fine with "hexadecimal" here.  I did not like "hex".

--

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

On Thu, Nov 18, 2010 at 3:00 PM, Alexander Belopolsky
 wrote:
..
>> I really think of them as hex or hexadecimal digits, just as 0-9 are 
>> decimal, not base 10 digits.
>>
>
> I am fine with "hexadecimal" here.  I did not like "hex".

If you think about it, "hexadecimal digit" is a twice oxymoron because
both "decimal" and "digit" imply base 10. :-)  It does look like the
most widely used term, nevertheless.

--

___
Python tracker 

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

[issue10456] unittest.main(verbosity=2) broke in python31, worked when I had python27

[Terry Herron]

New submission from Terry Herron :

The unittest.py module no longer accepts verbosity=2 when calling main.  This 
worked in Python27.  Example...

 unittest.main(verbosity=2)
 

## THE FIX IN unittest.py##
CHANGE FROM:
1547   def __init__(self, module='__main__', defaultTest=None,
1548   argv=None, testRunner=TextTestRunner,
1549   testLoader=defaultTestLoader, exit=True):

1560   self.verbosity = 1

CHANGE TO:
1547   def __init__(self, module='__main__', defaultTest=None,
1548   argv=None, testRunner=TextTestRunner,
1549   testLoader=defaultTestLoader, exit=True, verbosity=1):

1560   self.verbosity = verbosity

--
messages: 121492
nosy: teherr
priority: normal
severity: normal
status: open
title: unittest.main(verbosity=2) broke in python31, worked when I had python27
type: behavior
versions: Python 3.1

___
Python tracker 

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

[issue10456] unittest.main(verbosity=2) broke in python31, worked when I had python27

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti, michael.foord

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Raymond Hettinger]

Raymond Hettinger  added the comment:

The choice between ValueError and TypeError can sometimes be ambiguous and seem 
arbitrary and I understand why you're gravitating towards ValueError (because 
it works some values and not others), but in this case the API is already fixed 
by what hash() does elsewhere.

It is no fair to users to have to wrap hash(x) calls with a try/except that 
catches both exceptions.  So, we should still to a consistent hash API:

  >>> hash([])
  Traceback (most recent call last):
File "", line 1, in 
  hash([])
  TypeError: unhashable type: 'list'

In this case, practicality beats purity and released beats unreleased.

--
status: closed -> open

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
assignee: skrah -> rhettinger

___
Python tracker 

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

[issue10456] unittest.main(verbosity=2) broke in python31, worked when I had python27

[R. David Murray]

R. David Murray  added the comment:

2.7 is post-3.1.  This works as you expect in 3.2.  This is, it is a new 
feature in both 2.7 and 3.2.

(NB: this is why I wanted 3.2 to come out close to 2.7, but fortunately this is 
the first report like this I think we've gotten.)

--
nosy: +r.david.murray
resolution:  -> out of date
status: open -> closed

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Terry J. Reedy]

Terry J. Reedy  added the comment:

0 through ... is fine with me.

Yes, hex numeral would be more accurate than hex digit.

--

___
Python tracker 

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

[issue5421] Irritating error message by socket's sendto method

[Vetoshkin Nikita]

Vetoshkin Nikita  added the comment:

Here's a patch, which performs argument checking in a way to be able to provide 
better error message like that:

>>> my_socket.sendto("No Umlaut", ("localhost", 514))
Traceback (most recent call last):
  File "", line 1, in 
TypeError: 'str' does not support the buffer interface

--
keywords: +patch
nosy: +nvetoshkin
Added file: http://bugs.python.org/file19635/issue5421.diff

___
Python tracker 

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

[issue10356] decimal.py: hash of -1

[Stefan Krah]

Stefan Krah  added the comment:

Raymond Hettinger  wrote:
> The choice between ValueError and TypeError can sometimes be ambiguous and 
> seem arbitrary and I understand why you're gravitating towards ValueError 
> (because it works some values and not others), but in this case the API is 
> already fixed by what hash() does elsewhere.
> 
> It is no fair to users to have to wrap hash(x) calls with a try/except that 
> catches both exceptions.  So, we should still to a consistent hash API:
> 
>   >>> hash([])
>   Traceback (most recent call last):
> File "", line 1, in 
>   hash([])
>   TypeError: unhashable type: 'list'
> 
> In this case, practicality beats purity and released beats unreleased.

Ok, this makes sense. I can revert the commit unless you prefer to handle
it yourself.

--

___
Python tracker 

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

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

[Mihai Capotă]

Changes by Mihai Capotă :


--
nosy: +mihaic

___
Python tracker 

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

[issue7584] datetime.rfcformat() for Date and Time on the Internet

[Mihai Capotă]

Changes by Mihai Capotă :


--
nosy: +mihaic

___
Python tracker 

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

[issue10183] test_concurrent_futures failure on Windows

[Brian Quinlan]

Brian Quinlan  added the comment:

Could you try rerunning the tests with the attached patch? It could be that 
your machines are just terribly slow at starting new Python instances.

--
keywords: +patch
Added file: http://bugs.python.org/file19636/timing.patch

___
Python tracker 

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

[issue4153] Unicode HOWTO up to date?

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> Yes, hex numeral would be more accurate than hex digit.

Stick with hex digit.   We've used that phraseology for a long time.  See 
string.hexdigits for example.  And "hex numeral" just sounds weird -- it makes 
me do a double-take to see if there was some special implied meaning.

--
nosy: +rhettinger

___
Python tracker 

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

[issue10441] some stdlib modules need to be updated to handle SSL certificate validation

[david]

david  added the comment:

On 19 November 2010 04:40, Martin v. Löwis  wrote:
>
> Martin v. Löwis  added the comment:
>
>>> This may not be satisfying to users. For example, our Windows
>>> distribution doesn't ship with any certicates (AFAIK); I have no
>>> clue where exactly OpenSSL would be looking for them, either.
>>> People worried about this problem probably would want a way to
>>> fill the list of trusted CA certificates.
>>>
>>
>> Martin does it matter?
>> To be honest I don't know about that many client side python windows
>> applications for which this is a problem for. Maybe I am mistaken.
>
> I can't understand why you are saying that. The very same issues
> that people perceive as problems on Unix ("users can be victim
> to man in the middle attack") also exist on Windows. If you run
> a Python script that does https on Windows, you can *also* be
> MITM-victim (as likely as you can on Unix, that is).
>
> Or are you suggesting that Python Windows applications don't use SSL?
>
>> If
>> this is the case, then how do these projects work at the moment? (or
>> do they just not care about this...) .
>
> "The projects" may be scripts that somebody developed that never get
> released. But yes, most people ignore/accept the problem (often as
> gruntingly as the Unix users).
>
>> However, they could bundle
>> their own certificates, so I don't see this as an issue.
>
> Who is "they"? Most people get their Python binaries from python.org,
> and they don't build "applications" from it, but run "scripts".
>
>> However, you seem confused here:
>> " I have no
>>> clue where exactly OpenSSL would be looking for them, either.
>>> People worried about this problem probably would want a way to
>>> fill the list of trusted CA certificates."
>>
>> Erh, those people can already do this, but the problem is by default
>> none are selected.
>
> You misunderstood. I was not proposing that scripts provide a CA
> list, but that users might deploy a CA list into their Python
> installation, which is then picked up in the same way as you are asking
> for on Ubuntu.

No I did not misunderstand at all.
I am pushing for safer defaults or a way to enable safe defaults.
Having to tamper with my python path and point at a modified version
of the ssl module doesn't sound like fun.

OH windows users those guys. Well if they don't have any certificates
at the moment and they don't know this, perhaps some one should tell
them?
I don't know I am not a windows python user.

--
title: some stdlib modules need to be updated to handle SSL certificate 
validation -> some stdlib modules need to be updated to handle SSL certificate 
validation

___
Python tracker 

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

[issue8028] self.terminate() from a multiprocessing.Process raises AttributeError exception

[5houston]

5houston  added the comment:

Hi.
I tried my code (minCrashing.py) in windows using python 3.1.2, 2.3alpha4 and 
3.1.3rc1
The behaviour is deeply different from linux 3.1.2.
I think it's a bug.
What do you think about it?

--
versions: +Python 3.2 -Python 3.1

___
Python tracker 

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

[issue9312] Fix usage of :option: markup in stdlib ReST docs

[Eli Bendersky]

Eli Bendersky  added the comment:

Éric,

I went over both the diffs and the HTML output from "make clean html" on the 
latest 3.2 trunk. Looks good to me!

Just a tiny nit re unittest.rst, where it says "supports three command-line 
options". This is the kind of comment that gets left behind when new options 
are added. I see no added value explicitly saying there are 3 options as 
opposed to "supports the following command-line options", and there's less 
chance for future mistakes. It's also more consistent with the list of options 
for "discover" a bit later in the same document. This is totally a stylistic 
issue, of course, so IMVHO :-)

Oh, and another thing about unittest.rst: in 24.3.9 where it says "The -c 
command-line option to unittest", for some reason the -c didn't get linked to 
the option, although I think you intended it to, since you marked it as :option:

P.S: the program/cmdoption combo idea was Georg's.

--

___
Python tracker 

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