[Python-Dev] Summary of Python tracker Issues

2015-08-14 Thread Python tracker 

ACTIVITY SUMMARY (2015-08-07 - 2015-08-14)
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:
  open5002 (+10)
  closed 31627 (+32)
  total  36629 (+42)

Open issues with patches: 2244 


Issues opened (34)
==

#23530: os and multiprocessing.cpu_count do not respect cpuset/affinit
http://bugs.python.org/issue23530  reopened by serhiy.storchaka

#24745: Better default font for editor
http://bugs.python.org/issue24745  reopened by ned.deily

#24828: Segfault when using store-context AST node in a load context
http://bugs.python.org/issue24828  opened by xmorel

#24829: Use interactive input even if stdout is redirected
http://bugs.python.org/issue24829  opened by Drekin

#24831: Load average in test suite too high
http://bugs.python.org/issue24831  opened by skrah

#24832: Issue building viewable docs with newer sphinx (default theme 
http://bugs.python.org/issue24832  opened by r.david.murray

#24833: IDLE tabnanny check fails
http://bugs.python.org/issue24833  opened by Сергей Лисов

#24834: pydoc should display the expression for a builtin argument def
http://bugs.python.org/issue24834  opened by larry

#24836: Consistent failure in test_email on OS X Snow Leopard buildbot
http://bugs.python.org/issue24836  opened by larry

#24837: await process.wait() does not work with a new_event_loop
http://bugs.python.org/issue24837  opened by chetan

#24838: tarfile.py: fix GNU and USTAR formats to properly handle paths
http://bugs.python.org/issue24838  opened by Roddy Shuler

#24840: implement bool conversion for enums to prevent odd edge case
http://bugs.python.org/issue24840  opened by novas0x2a

#24841: Some test_ssl network tests fail if svn.python.org is not acce
http://bugs.python.org/issue24841  opened by vlee

#24842: Mention SimpleNamespace in namedtuple docs
http://bugs.python.org/issue24842  opened by cvrebert

#24844: Python 3.5rc1 compilation error with Apple clang 4.2 included 
http://bugs.python.org/issue24844  opened by dabeaz

#24845: IDLE functional/integration testing
http://bugs.python.org/issue24845  opened by markroseman

#24846: Add tests for ``from ... import ...` code
http://bugs.python.org/issue24846  opened by brett.cannon

#24847: Can't import tkinter in Python 3.5.0rc1
http://bugs.python.org/issue24847  opened by mrabarnett

#24848: Warts in UTF-7 error handling
http://bugs.python.org/issue24848  opened by serhiy.storchaka

#24849: Add __len__ to map, everything in itertools
http://bugs.python.org/issue24849  opened by flying sheep

#24850: syslog.syslog() does not return error when unable to send the 
http://bugs.python.org/issue24850  opened by Cyril Bouthors

#24851: infinite loop in faulthandler._stack_overflow
http://bugs.python.org/issue24851  opened by Paul Murphy

#24852: Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix
http://bugs.python.org/issue24852  opened by John Hagen

#24853: Py_Finalize doesn't clean up PyImport_Inittab
http://bugs.python.org/issue24853  opened by Alex Budovski

#24857: mock: Crash on comparing call_args with long strings
http://bugs.python.org/issue24857  opened by Wilfred.Hughes

#24858: python3 -m test -ugui -v test_tk gives 3 failures under Debian
http://bugs.python.org/issue24858  opened by lac

#24859: ctypes.Structure bit order is reversed - counts from right
http://bugs.python.org/issue24859  opened by zeero

#24860: handling of IDLE 'open module' errors
http://bugs.python.org/issue24860  opened by markroseman

#24861: deprecate importing components of IDLE
http://bugs.python.org/issue24861  opened by markroseman

#24862: subprocess.Popen behaves incorrect when moved in process tree
http://bugs.python.org/issue24862  opened by Andre Merzky

#24864: errors writing to stdout during interpreter exit exit with sta
http://bugs.python.org/issue24864  opened by rbcollins

#24866: Boolean representation of Q/queue objects does not fit behavio
http://bugs.python.org/issue24866  opened by Frunit

#24867: Asyncio Task.get_stack fails with native coroutines
http://bugs.python.org/issue24867  opened by habilain

#24868: Python start
http://bugs.python.org/issue24868  opened by jack



Most recent 15 issues with no replies (15)
==

#24868: Python start
http://bugs.python.org/issue24868

#24853: Py_Finalize doesn't clean up PyImport_Inittab
http://bugs.python.org/issue24853

#24848: Warts in UTF-7 error handling
http://bugs.python.org/issue24848

#24846: Add tests for ``from ... import ...` code
http://bugs.python.org/issue24846

#24841: Some test_ssl network tests fail if svn.python.org is not acce
http://bugs.python.org/issue24841

#24834: pydoc should display the expression for a builtin argument def
http://bugs.python.org/issue24834

#24833: IDLE tabnanny check fails
http://bugs.python.org/issue24833

#24829: Use interactive input even if stdout is redire

[Python-Dev] Differences between Python's OpenSSL in SVN and OpenSSL's in GitHub

2015-08-14 Thread Guzman-ballen, Andres 
Hello Python Developers!

Why is it that the OpenSSL v1.0.2d that is found on Python's SVN 
repo is quite 
different from what OpenSSL has on their GitHub 
repository for OpenSSL 
v1.0.2d? I am asking because I am able to successfully download OpenSSL's 
GitHub version during the cpython build process but when I try to build 
cpython, I get failures because Visual Studio isn't able to find files like 
openssl/opensslconf.h and this is because Python's OpenSSL version in SVN is 
the only one that has a directory inside the include directory. The GitHub repo 
is missing this directory however, and these are not the only differences.

If I checkout the GitHub version and then replace it with what is in the SVN 
repo, you get these untracked files.

MINFO
Makefile
Makefile.bak
apps/CA.pl
apps/md4.c
crypto/buildinf.h
crypto/buildinf.h.orig
crypto/buildinf_amd64.h
crypto/buildinf_x86.h
crypto/opensslconf.h
crypto/opensslconf.h.bak
crypto/opensslconf_amd64.h
crypto/opensslconf_x86.h
inc64/
include/openssl/
ms/bcb.mak
ms/libeay32.def
ms/nt.mak
ms/nt64.mak
ms/ntdll.mak
ms/ssleay32.def
ms/uptable.asm
ms/uptable.obj
ms/version32.rc
out64/
test/bftest.c
test/bntest.c
test/casttest.c
test/constant_time_test.c
test/destest.c
test/dhtest.c
test/dsatest.c
test/ecdhtest.c
test/ecdsatest.c
test/ectest.c
test/enginetest.c
test/evp_extra_test.c
test/evp_test.c
test/evptests.txt
test/exptest.c
test/heartbeat_test.c
test/hmactest.c
test/ideatest.c
test/jpaketest.c
test/md2test.c
test/md4test.c
test/md5test.c
test/mdc2test.c
test/randtest.c
test/rc2test.c
test/rc4test.c
test/rc5test.c
test/rmdtest.c
test/rsa_test.c
test/sha1test.c
test/sha256t.c
test/sha512t.c
test/shatest.c
test/srptest.c
test/ssltest.c
test/v3nametest.c
test/verify_extra_test.c
test/wp_test.c
tmp/
tmp32/
tmp64/
tools/c_rehash

Does anyone know why this is the case? What was the motivation behind these 
changes? Thanks!

Andres Guzman-Ballen
Scripting Analyzers & Tools Team
Intel Americas, Inc.
1906 Fox Dr, Champaign IL 61820
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Differences between Python's OpenSSL in SVN and OpenSSL's in GitHub

2015-08-14 Thread Zachary Ware 
On Fri, Aug 14, 2015 at 10:56 AM, Guzman-ballen, Andres
 wrote:
> Hello Python Developers!
>
> Why is it that the OpenSSL v1.0.2d that is found on Python’s SVN repo is
> quite different from what OpenSSL has on their GitHub repository for OpenSSL
> v1.0.2d?

The reason for the difference is to avoid requiring Perl to be
installed to be able to build Python.  The svn.python.org version of
openssl-1.0.2d at revision 89058should match 1.0.2d from Github (if it
doesn't that's a bug in OpenSSL's packaging or my checking it into
SVN).  Revision 89059 checks in all of the changes, all of which are
made by running 'PCbuild\prepare_ssl.py' on the vanilla sources, and
you should be able to produce the same set of changes by running
'PCbuild\prepare_ssl.py' over the sources checked out from Github.
Note that to run that script successfully, you'll need to have the
Visual Studio environment set up ('PCbuild\env.bat' will do it for
you), Perl and NASM on your PATH, and run the script with Python 3.4
or later.

Hope this answers your question,
-- 
Zach
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Differences between Python's OpenSSL in SVN and OpenSSL's in GitHub

2015-08-14 Thread Steve Dower 

On 14Aug2015 0856, Guzman-ballen, Andres wrote:

Hello Python Developers!

Why is it that the OpenSSL v1.0.2d that is found on Python’s SVN repo
 is quite
different from what OpenSSL has on their GitHub repository
 for OpenSSL
v1.0.2d? I am asking because I am able to successfully download
OpenSSL’s GitHub version during the cpython build process but when I try
to build cpython, I get failures because Visual Studio isn’t able to
find files like openssl/opensslconf.h and this is because Python’s
OpenSSL version in SVN is the only one that has a directory inside the
include directory. The GitHub repo is missing this directory however,
and these are not the only differences.

If I checkout the GitHub version and then replace it with what is in the
SVN repo, you get these untracked files.

 MINFO

 Makefile

 Makefile.bak

 apps/CA.pl

 apps/md4.c

 crypto/buildinf.h

 crypto/buildinf.h.orig

 crypto/buildinf_amd64.h

 crypto/buildinf_x86.h

 crypto/opensslconf.h

 crypto/opensslconf.h.bak

 crypto/opensslconf_amd64.h

 crypto/opensslconf_x86.h

 inc64/

 include/openssl/

 ms/bcb.mak

 ms/libeay32.def

 ms/nt.mak

 ms/nt64.mak

 ms/ntdll.mak

 ms/ssleay32.def

 ms/uptable.asm

 ms/uptable.obj

 ms/version32.rc

 out64/

 test/bftest.c

 test/bntest.c

 test/casttest.c

 test/constant_time_test.c

 test/destest.c

 test/dhtest.c

 test/dsatest.c

 test/ecdhtest.c

 test/ecdsatest.c

 test/ectest.c

 test/enginetest.c

 test/evp_extra_test.c

 test/evp_test.c

 test/evptests.txt

 test/exptest.c

 test/heartbeat_test.c

 test/hmactest.c

 test/ideatest.c

 test/jpaketest.c

 test/md2test.c

 test/md4test.c

 test/md5test.c

 test/mdc2test.c

 test/randtest.c

 test/rc2test.c

 test/rc4test.c

 test/rc5test.c

 test/rmdtest.c

 test/rsa_test.c

 test/sha1test.c

 test/sha256t.c

 test/sha512t.c

 test/shatest.c

 test/srptest.c

 test/ssltest.c

 test/v3nametest.c

 test/verify_extra_test.c

 test/wp_test.c

 tmp/

 tmp32/

 tmp64/

 tools/c_rehash

Does anyone know why this is the case? What was the motivation behind
these changes? Thanks!

Andres Guzman-Ballen

Scripting Analyzers & Tools Team

Intel Americas, Inc.

1906 Fox Dr, Champaign IL 61820




To build OpenSSL on Windows you also need a copy of Perl and you need to 
run the preparation script to generate some extra code files. Otherwise 
you don't get a Windows makefile (which we don't use anymore because it 
builds significantly faster and more reliably with a Visual C++ project) 
and the generated assembly code.


The copy we have in SVN has already had these scripts generated, but 
nothing else should be different from the original repository. It's 
possible you got a slightly different version out of github? I believe 
we use their released tarballs, but Zach will know for sure as he did 
the last update IIRC.


Cheers,
Steve

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