Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

2015-11-27 Thread Stephen J. Turnbull
Nick Coghlan writes:

 > This is a significant rewrite that switches the PEP to a Standards
 > Track PEP proposing two new features for 2.7.12+: an
 > "ssl._verify_https_certificates()" configuration function, and a
 > "PYTHONHTTPSVERIFY" environment variable (although writing them
 > together like that makes me wonder if the latter should now be
 > "PYTHONVERIFYHTTPS" instead).

+1 on the same order of "words" in the function name and the
evnironment variable.  I tend to prefer
"ssl._https_verify_certificates" since these aren't "HTTPS
certificates".

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

2015-11-27 Thread Cory Benfield

> On 27 Nov 2015, at 06:04, Nick Coghlan  wrote:
> 
> Feature: Configuration API
> ==
> 
> This change is proposed for inclusion in CPython 2.7.12 and later CPython 
> 2.7.x
> releases. It consists of a new ``ssl._verify_https_certificates()`` to specify
> the default handling of HTTPS certificates in standard library client 
> libraries.
> 
> It is not proposed to forward port this change to Python 3, so Python 3
> applications that need to support skipping certificate verification will still
> need to define their own suitable security context.
> 
> Feature detection
> -
> 
> The marker attribute on the ``ssl`` module related to this feature is the
> ``ssl._verify_https_certificates`` function itself.
> 
> Specification
> -
> 
> The ``ssl._verify_https_certificates`` function will work as follows::
> 
>def _verify_https_certificates(enable=True):
>"""Verify server HTTPS certificates by default?"""
>global _create_default_https_context
>if enable:
>_create_default_https_context = create_default_context
>else:
>_create_default_https_context = _create_unverified_context
> 
> If called without arguments, or with ``enable`` set to a true value, then
> standard library client modules will subsequently verify HTTPS
> certificates by default, otherwise they will skip verification.

Perhaps I missed this, Nick, but what happens if multiple third party libraries 
apply updates to call this function in incompatible ways? For example, if you 
depend on libfoo which calls ssl._verify_https_certificates(False) and libbar 
which calls ssl._verify_https_certificates(True)? Is it…last import wins?


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

2015-11-27 Thread Nick Coghlan
On 27 November 2015 at 18:47, Cory Benfield  wrote:
> Perhaps I missed this, Nick, but what happens if multiple third party 
> libraries apply updates to call this function in incompatible ways? For 
> example, if you depend on libfoo which calls 
> ssl._verify_https_certificates(False) and libbar which calls 
> ssl._verify_https_certificates(True)? Is it…last import wins?

Last import wins, but libaries shouldn't be mutating process global
state as a side effect of import - like the sys module, the ssl module
configuration should only be modified (directly or indirectly) from
__main__.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] The AttributeError/__getattr__ mechanism

2015-11-27 Thread 王珺
Hello everyone:

I'm suggesting a modification to the AttributeError/__getattr__ mechanism,
see issue25634:
http://bugs.python.org/issue25634

I used __getattr__ sometimes, and *descriptor* especially *property* is so
widely used. I wonder whether someone
had encountered the same problem with me.

However, this is a complicated problem including performance issues, and
backward compatibility.

Thanks for your attention,
Jun Wang
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] The AttributeError/__getattr__ mechanism

2015-11-27 Thread Victor Stinner
Hi,

As R. David Murray wrote on the issue, the python-ideas mailing list
is better suited to start such discussion ;-)

Victor

2015-11-27 9:40 GMT+01:00 王珺 :
> Hello everyone:
>
> I'm suggesting a modification to the AttributeError/__getattr__ mechanism,
> see issue25634:
> http://bugs.python.org/issue25634
>
> I used __getattr__ sometimes, and descriptor especially property is so
> widely used. I wonder whether someone
> had encountered the same problem with me.
>
> However, this is a complicated problem including performance issues, and
> backward compatibility.
>
> Thanks for your attention,
> Jun Wang
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Summary of Python tracker Issues

2015-11-27 Thread Python tracker

ACTIVITY SUMMARY (2015-11-20 - 2015-11-27)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open5263 ( +3)
  closed 32238 (+57)
  total  37501 (+60)

Open issues with patches: 2312 


Issues opened (41)
==

#20923: Explain ConfigParser 'valid section name' and .SECTCRE
http://bugs.python.org/issue20923  reopened by terry.reedy

#25684: ttk.OptionMenu radiobuttons aren't unique between two instance
http://bugs.python.org/issue25684  opened by Bryan.Oakley

#25685: Inefficiency with SocketHandler - may send log record message 
http://bugs.python.org/issue25685  opened by Marvin Greenberg

#25687: Error during test case and tearDown
http://bugs.python.org/issue25687  opened by bennoleslie

#25690: Replacement for unittest.mock.mock_open
http://bugs.python.org/issue25690  opened by Niv Ben-David

#25694: test.libregrtest not installed
http://bugs.python.org/issue25694  opened by Arfrever

#25696: "make -j9 install" fails because bininstall target requires th
http://bugs.python.org/issue25696  opened by haypo

#25698: test regressions introduced with the fix for #22995
http://bugs.python.org/issue25698  opened by doko

#25699: Easier way to specify reduced globals for doctest
http://bugs.python.org/issue25699  opened by John.Mark.Vandenberg

#25701: Document that tp_setattro and tp_setattr are used for deleting
http://bugs.python.org/issue25701  opened by serhiy.storchaka

#25702: Link Time Optimizations support for GCC and CLANG
http://bugs.python.org/issue25702  opened by alecsandru.patrascu

#25704: Update the devguide to 3.5
http://bugs.python.org/issue25704  opened by matrixise

#25707: Add the close method for ElementTree.iterparse() object
http://bugs.python.org/issue25707  opened by serhiy.storchaka

#25708: runpy hides traceback for some exceptions
http://bugs.python.org/issue25708  opened by sleepycal

#25709: Problem with string concatenation and utf-8 cache.
http://bugs.python.org/issue25709  opened by Árpád Kósa

#25710: zipimport is not PEP 3147 or PEP 488 compliant
http://bugs.python.org/issue25710  opened by byrnes

#25711: Rewrite zipimport from scratch
http://bugs.python.org/issue25711  opened by brett.cannon

#25713: Setuptools included with 64-bit Windows installer is outdated
http://bugs.python.org/issue25713  opened by James.Paget

#25714: Consider isinstance(..., numbers.Integral) instead of isinstan
http://bugs.python.org/issue25714  opened by posita

#25715: Python 3.5.1 installer shows wrong upgrade path
http://bugs.python.org/issue25715  opened by steve.dower

#25716: typeobject.c call_method & call_maybe can leak references on '
http://bugs.python.org/issue25716  opened by Myron Walker

#25717: tempfile.TemporaryFile fails when dir option set to directory 
http://bugs.python.org/issue25717  opened by Hans Lawrenz

#25718: itertools.accumulate __reduce__/__setstate__ bug
http://bugs.python.org/issue25718  opened by arigo

#25719: Deprecate spitfire benchmark
http://bugs.python.org/issue25719  opened by florin.papa

#25720: Fix curses module compilation with ncurses6
http://bugs.python.org/issue25720  opened by donmez

#25723: ConfigParser should never write broken configurations
http://bugs.python.org/issue25723  opened by spaceone

#25724: SSLv3 test failure on Ubuntu 16.04 LTS
http://bugs.python.org/issue25724  opened by mdeslaur

#25726: sys.setprofile / sys.getprofile asymetry
http://bugs.python.org/issue25726  opened by stefan

#25728: email parser ignores inner multipart boundary when outer messa
http://bugs.python.org/issue25728  opened by forest

#25729: update pure python datetime.timedelta creation
http://bugs.python.org/issue25729  opened by bdkearns

#25730: invisible sidebar content with code snippets
http://bugs.python.org/issue25730  opened by xwhhsprings

#25731: Assigning and deleting __new__ attr on the class does not allo
http://bugs.python.org/issue25731  opened by Stanisław Skonieczny (Uosiu)

#25732: functools.total_ordering does not correctly implement not equa
http://bugs.python.org/issue25732  opened by David Seddon

#25733: Idle does not handle non-standard compile errors
http://bugs.python.org/issue25733  opened by ppperry

#25735: math.factorial doc should mention integer return type
http://bugs.python.org/issue25735  opened by John.Yeung

#25738: http.server doesn't handle RESET CONTENT status correctly
http://bugs.python.org/issue25738  opened by spaceone

#25739: Add PAYLOAD_TOO_LARGE / URI_TOO_LONG (new name in RFC 7231)
http://bugs.python.org/issue25739  opened by spaceone

#25740: multiple issues in http.client
http://bugs.python.org/issue25740  opened by spaceone

#25741: Usual Installation Directory
http://bugs.python.org/issue25741  opened by firatozgul

#25742: locale.setlocale does not work with unicode strings
http://bugs.python.org/issue25742  opened by tierlieb

#25743: Clarify exactly what \

[Python-Dev] ACTIVITY SUMMARY (2015-11-20 - 2015-11-27)

2015-11-27 Thread Laura Creighton
My mailer just barfed trying to read that summary.
The problem is that the mail comes out with the encoding:
Content-Type: text/plain; charset="us-ascii"
 but then wants to print 'http://bugs.python.org/issue25709  opened 
 by Árpád Kósa'

Can we change the encoding to utf-8 ?

Laura


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com