Re: Posts from gmane no longer allowed?
On 9/26/21 20:38, Grant Edwards wrote: On 2021-09-26, Ethan Furman wrote: On 9/26/21 10:34 AM, Grant Edwards wrote: On 2021-09-26, Ethan Furman wrote: I am unaware of a change in the newsgroup <--> mailing list policy, and other newsgroup posts were coming through last week (it's been a light weekend). We're not talking about the usenet<-->list gateway. My first _guess_ would be that Mailman started refusing emailed posts from the gmane server to python-list, and that triggered the gmane server to stop accepting posts for python-list. I readily admit I may not understand, or know, all the usenet jargon, Once again, there is no Usenet involved. Gmane.io is an NNTP server, and NNTP is _also_ used by Usenet servers, but Gmane isn't part of Usenet and doesn't implement any of the Usenet peering "news" protocols. but looking at the Mailman server for Python list I see it is still fully configured to talk with News.FU-Berlin.DE, newsgroup comp.lang.python. This has nothing to do with Usenet servers or their connections to python-list. From the list's POV, gmane.io is a "normal" email subscriber who just happens to archive all the articles it receives. I should never have mentioned that gmane.io does NNTP -- it just seems to have confused everybody. When a gmane.io user submits a post, the post arrives at python-list by normal email channels having been sent via SMTP by the gmane.io server "From:" the user (who, IIRC, has to be subscribed to the list). I have been in touch with the administrator of gmane. It appears that posting from python-list to gmane has been deliberately disabled, at least temporarily, with cause. I'll see if we can resolve the problem. -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.12 and 3.6.15 security updates now available
Python 3.7.12 and 3.6.15, the lastest security fix rollups for Python 3.7 and Python 3.6, are now available. You can find the release files, links to the changelogs, and more information here: https://www.python.org/downloads/release/python-3712/ https://www.python.org/downloads/release/python-3615/ These releases are source code only; Windows and macOS binary installers are not provided for security fix releases. Note that Python 3.9 is now the latest feature release series of Python 3. You should consider upgrading to 3.9 as soon as practical. Get the latest release of 3.9.x here: https://www.python.org/downloads/ Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf-landing/ -- Ned Deily n...@python.org -- [] signature.asc Description: Message signed with OpenPGP -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.10 and 3.6.13 security updates now available
Python 3.7.10 and 3.6.13, the lastest security fix rollups for Python 3.7 and Python 3.6, are now available. You can find the release files, links to the changelogs, and more information here: https://www.python.org/downloads/release/python-3710/ https://www.python.org/downloads/release/python-3613/ These releases are source code only; Windows and macOS binary installers are not provided for security fix releases. Note that Python 3.9 is now the latest feature release series of Python 3. You should consider upgrading to 3.9 as soon as practical. Get the latest release of 3.9.x here: https://www.python.org/downloads/ Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf-landing/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: IDLE 3.8.4 [was 3.8.3] -- bug report
On 2020-08-03 15:37, Halvard Tislavoll wrote:
> I'am dealing with a bug
[...]
> Python 3.8.4 (default, Jul 20 2020, 20:20:14)
> IDLE 3.8.4
>
> I have been using IDLE for many years. But now I can not do it.
>
> Example:
> I write a heading for a python script in my text editor, xed and save as
> 'test.py'.
> ..
> #! /usr/bin/env python
> # -*- coding: utf-8 -*-
>
> # ... pandas-techniques-python-data-manipulation/
>
> import pandas as pd
> import numpy as np
>
> #---
> ...
> Then I open 'test.py' in IDLE. Everything looks normal.
>
> I am testing whether it is possible to save with the shortcut ctrl-s. OK.
>
> But then I write the following line:
>
> print ("\ n # 1 - Boolean Indexing in Pandas \ n")
>
> Result:
> storage no longer works. And IDLE becomes useless!
>
> The problem is that print statement no longer support my sign "-" U + 2013 EN
> DASH
>
> but this sign goes well; "-" U + 002D HYPHEN-MINUS
See https://bugs.python.org/issue41300
The problem was introduced in Python 3.8.4 (released 2020-07-13) and has
been fixed in 3.8.5 which was released 2020-07-20.
--
https://mail.python.org/mailman/listinfo/python-list
Re: Installing Python 3.8.3 with tkinter
On 2020-07-23 00:30, Klaus Jantzen wrote: > On 7/22/20 11:05 PM, Ned Deily wrote: >> On 2020-07-22 06:20, Klaus Jantzen wrote: >>> Trying to install Python 3.8.3 with tkinter I run configure with the >>> following options >>> >>> ./configure --enable-optimizations --with-ssl-default-suites=openssl >>> --with-openssl=/usr/local --enable-loadable-sqlite-extensions >>> --with-pydebug --with-tcltk-libs='-L/opt/ActiveTcl-8.6/lib/tcl8.6' >>> --with-tcltk-includes='-I/opt/ActiveTcl-8.6/include' >>> >>> Running Python gives the following information >> [...] >>> How do that correctly? >> Try --with-tcltk-libs='-L/opt/ActiveTcl-8.6/lib -ltcl8.6 -ltk8.6' >> >> > Thank you for your suggestion; unfortunately it did not help. Without knowing exactly how the /opt/ActiveTcl-8.6 directory is laid out, we can only guess at what the right options should be. The basic idea is that there needs to be one or more -I entries that covers the top-level directory(ies) with Tcl and Tk include files and for the libraries there needs to be a -L entry for the directory and a -l entry for the name of the shared library (minus the "lib" prefix), assuming Tcl and Tk were built with --enable-shared. Usually both libraries are installed into the same directory, in which case you only need one -L as above. If they do not have a common parent, you would need to specify each separately, like -L/libtclparent -l tcl8.6 -L/libtkparent -ltk8.6. If that doesn't help, you could display the show the contents of the include and directories here: ls -l /opt/ActiveTcl-8.6/include /opt/ActiveTcl-8.6/lib Also exactly what platform are you building on? And, btw, Python 3.8.5 is now current. -- https://mail.python.org/mailman/listinfo/python-list
Re: Installing Python 3.8.3 with tkinter
On 2020-07-22 06:20, Klaus Jantzen wrote: > Trying to install Python 3.8.3 with tkinter I run configure with the > following options > > ./configure --enable-optimizations --with-ssl-default-suites=openssl > --with-openssl=/usr/local --enable-loadable-sqlite-extensions > --with-pydebug --with-tcltk-libs='-L/opt/ActiveTcl-8.6/lib/tcl8.6' > --with-tcltk-includes='-I/opt/ActiveTcl-8.6/include' > > Running Python gives the following information [...] > How do that correctly? Try --with-tcltk-libs='-L/opt/ActiveTcl-8.6/lib -ltcl8.6 -ltk8.6' -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.8 and 3.6.11 now available - last 3.7.x bugfix release
https://discuss.python.org/t/python-3-7-8-and-3-6-11-now-available-last-3-7-x-bugfix-release/4583 -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.8rc1 and 3.6.11rc1 are now available for testing
Details here: https://discuss.python.org/t/python-3-7-8rc1-and-3-6-11rc1-are-now-available-for-testing/4467 https://www.python.org/downloads/release/python-378rc1/ https://www.python.org/downloads/release/python-3611rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.7 is now available
https://discuss.python.org/t/python-3-7-7-is-now-available/3682 https://www.python.org/downloads/release/python-377/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: [Python-Dev] [RELEASE] Python 3.7.7rc1 is now available for testing
On Mar 4, 2020, at 23:39, Jonathan Goble wrote: >> On Wed, Mar 4, 2020 at 10:05 PM Ned Deily wrote: >> On Mar 4, 2020, at 17:17, Jonathan Goble wrote: >> > On Wed, Mar 4, 2020 at 1:02 PM Ned Deily wrote: >> > Details here: >> >> https://discuss.python.org/t/python-3-7-7rc1-is-now-available-for-testing/3638 >> >> "Assuming no critical problems are found prior to 2020-02-10..." >> > I would like to know how you expect people to travel back in time to >> > report problems. :P >> >> python3.7 -m pip install guidos_time_machine >> >> If, for some reason that doesn't work, let's wait until 2020-03-10! > > Well, it works now! (if you substitute dashes for the underscores) > > https://pypi.org/project/guidos-time-machine/ > > Brand new package uploaded by Guido 36 minutes ago. Python is great for just-in-time agile development, especially in future tenths. -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: [Python-Dev] [RELEASE] Python 3.7.7rc1 is now available for testing
On Mar 4, 2020, at 17:17, Jonathan Goble wrote: > On Wed, Mar 4, 2020 at 1:02 PM Ned Deily wrote: > Details here: > >> https://discuss.python.org/t/python-3-7-7rc1-is-now-available-for-testing/3638 >> >> "Assuming no critical problems are found prior to 2020-02-10..." > I would like to know how you expect people to travel back in time to report > problems. :P python3.7 -m pip install guidos_time_machine If, for some reason that doesn't work, let's wait until 2020-03-10! -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.7rc1 is now available for testing
Details here: https://discuss.python.org/t/python-3-7-7rc1-is-now-available-for-testing/3638 https://www.python.org/downloads/release/python-377rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: Unable to install Flask-Mongoengine
On 2019-12-15 03:13, Test Bot wrote: I am unable to install *Flask-Mongoengine* using pip. Here are my specifications 1. *OS* => OSX 10.14.6 2. *Python* => Python 3.8.0 (Working in a virtualenv) 3. *Dependency Manager* => pip(19.3.1), setuptools(42.0.2) 3. *Flask-Mongoengine* => flask-mongoengine==0.9.5 I am inside my virtualenv and trying to install flask-mongoengine using (env) $ pip install flask-mongoengine==0.9.5 Here is my error distutils.errors.DistutilsError: Command '['/Users/onlinejudge95/Workspace/GitHub/alma-serv/env/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/var/folders/r7/pgqw605n55x5f9018rp72hsmgn/T/tmpgrvp80jd', '--quiet', 'rednose']' returned non-zero exit status 1. You are running into an issue caused by a change in setuptools: https://github.com/pypa/setuptools/issues/1934 It looks like the simplest solution is to first install the wheel package in your venv: pip install wheel pip install flask-mongoengine==0.9.5 Either that or install a previous version of setuptools. You may want to chime in on the discussion of that issue. -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.6rc1 and 3.6.10rc1 are now available for testing
Details here: https://discuss.python.org/t/python-3-7-6rc1-and-3-6-10rc1-are-now-available-for-testing/2835 https://www.python.org/downloads/release/python-376rc1/ https://www.python.org/downloads/release/python-3610rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.5 is now available
Python 3.7.5 is now available, the next maintenance release of Python 3.7. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-375/ Note that the next feature release of Python 3, Python 3.8.0, is also now available. Python 3.8 contains many new features and optimizations. You should consider upgrading to it. We plan to continue regular bugfix releases of Python 3.7.x through mid-year 2020 and provide security fixes for it until mid-year 2023. More details are available in PEP 537, the Python 3.7 Release Schedule (https://www.python.org/dev/peps/pep-0537/). Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.5rc1 is now available for testing
Python 3.7.5rc1 is now available for testing. 3.7.5rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no critical problems are found prior to 2019-10-14, no code changes are planned between now and the final release. This release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.5. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that this is a preview release and, thus, its use is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-375rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.4 is now available
Python 3.7.4 is now available. 3.7.4 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-374/ See the "What’s New In Python 3.7" document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.4 can be found in its change log: https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-4-final https://docs.python.org/3.7/whatsnew/3.7.html Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation: https://www.python.org/psf/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.4rc2 is now available for testing
Python 3.7.4rc2 is now available. 3.7.4rc2 is the second release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no further critical problems are found prior to 2019-07-08, no code changes are planned between this release candidate and the final release. The release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.4. Because of the small number of changes between rc1, the original release preview, and rc2, we are planning on an abbreviated exposure cycle so we can get the final release to you as soon as possible. We strongly encourage you to test your projects and report issues found to https://bugs.python.org/ as soon as possible. Please keep in mind that this is a preview release and, thus, is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-374rc2/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.9 security-fix release is now available
Python 3.6.9 is now available. 3.6.9 is the first security-only-fix release of Python 3.6. Python 3.6 has now entered the security fix phase of its life cycle. Only security-related issues are accepted and addressed during this phase. We plan to provide security fixes for Python 3.6 as needed through 2021, five years following its initial release. Security fix releases are produced periodically as needed and only provided in source code form; binary installers are not provided. We urge you to consider upgrading to the latest release of Python 3.7, the current fully-supported version. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-369/ https://www.python.org/downloads/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.4rc1 and 3.6.9rc1 are now available
Python 3.7.4rc1 and 3.6.9rc1 are now available. 3.7.4rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. 3.6.9rc1 is the release preview of the first security-fix release of Python 3.6. Assuming no critical problems are found prior to 2019-06-28, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.4 and security fixes in 3.6.9. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find the release files, a link to their changelogs, and more information here: https://www.python.org/downloads/release/python-374rc1/ https://www.python.org/downloads/release/python-369rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.3 is now available
https://blog.python.org/2019/03/python-373-is-now-available.html Python 3.7.3 is now available. Python 3.7.3 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find Python 3.7.3 here: https://www.python.org/downloads/release/python-373/ See the What’s New In Python 3.7 document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.3 can be found in its change log. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://docs.python.org/3.7/whatsnew/3.7.html https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-3-final https://www.python.org/psf/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.3rc1 is now available for testing.
Python 3.7.3rc1 is now available for testing. 3.7.3rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no critical problems are found prior to 2019-03-25, no code changes are planned between now and the final release. This release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.3. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that this is a preview release and, thus, its use is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-373rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.2 and 3.6.8 are now available
https://blog.python.org/2018/12/python-372-and-368-are-now-available.html Python 3.7.2 and 3.6.8 are now available. Python 3.7.2 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find Python 3.7.2 here: https://www.python.org/downloads/release/python-372/ See the What’s New In Python 3.7 document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.2 can be found in its change log. We are also happy to announce the availability of Python 3.6.8: https://www.python.org/downloads/release/python-368/ Python 3.6.8 is planned to be the last bugfix release of Python 3.6. Per our support policy, we plan to provide security fixes for Python 3.6 as needed through 2021, five years following its initial release. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://docs.python.org/3.7/whatsnew/3.7.html https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-2-final https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-8-final https://www.python.org/psf/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.2rc1 and 3.6.8rc1 now available for testing
https://blog.python.org/2018/12/python-372rc1-and-368rc1-now-available.html Python 3.7.2rc1 and 3.6.8rc1 are now available. 3.7.2rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. 3.6.8rc1 is the release preview of the next and last maintenance release of Python 3.6, the previous feature release of Python. Assuming no critical problems are found prior to 2018-12-20, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.2 and 3.6.8. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find these releases and more information here: https://www.python.org/downloads/release/python-372rc1/ https://www.python.org/downloads/release/python-368rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.1 and 3.6.7 are now available
On behalf of the Python development community and the Python 3.7 release team, we are pleased to announce the availability of Python 3.7.1. Python 3.7.1 is the first maintenance release of the newest feature release of the Python language. You can find Python 3.7.1 here: https://www.python.org/downloads/release/python-371/ See the What’s New In Python 3.7 document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.1 can be found in its change log: https://docs.python.org/3.7/whatsnew/3.7.html https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-1-final We are also happy to announce the availability of Python 3.6.7, the next maintenance release of Python 3.6: https://www.python.org/downloads/release/python-367/ Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.1rc2 and 3.6.7rc2 now available for testing
Python 3.7.1rc2 and 3.6.7rc2 are now available. 3.7.1rc2 is a release preview of the first maintenance release of Python 3.7, the latest feature release of Python. 3.6.7rc2 is a release preview of the next maintenance release of Python 3.6, the previous feature release of Python. Assuming no further critical problems are found prior to 2018-10-20, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.1 and 3.6.7. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find these releases and more information here: https://www.python.org/downloads/release/python-371rc2/ https://www.python.org/downloads/release/python-367rc2/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.1rc1 and 3.6.7rc1 now available for testing
Python 3.7.1rc1 and 3.6.7rc1 are now available. 3.7.1rc1 is the release preview of the first maintenance release of Python 3.7, the latest feature release of Python. 3.6.7rc1 is the release preview of the next maintenance release of Python 3.6, the previous feature release of Python. Assuming no critical problems are found prior to 2018-10-06, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.1 and 3.6.7. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find these releases and more information here: https://www.python.org/downloads/release/python-371rc1/ https://www.python.org/downloads/release/python-367rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Python 3.7.0 is now available! (and so is 3.6.6)
On behalf of the Python development community and the Python 3.7 release team, we are pleased to announce the availability of Python 3.7.0. Python 3.7.0 is the newest feature release of the Python language, and it contains many new features and optimizations. You can find Python 3.7.0 here: https://www.python.org/downloads/release/python-370/ Most third-party distributors of Python should be making 3.7.0 packages available soon. See the "What’s New In Python 3.7" document (https://docs.python.org/3.7/whatsnew/3.7.html) for more information about features included in the 3.7 series. Detailed information about the changes made in 3.7.0 can be found in its change log. Maintenance releases for the 3.7 series will follow at regular intervals starting in July of 2018. We hope you enjoy Python 3.7! P.S. We are also happy to announce the availability of Python 3.6.6, the next maintenance release of Python 3.6: https://www.python.org/downloads/release/python-366/ Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0rc1 and 3.6.6rc1 are now available
Python 3.7.0rc1 and 3.6.6rc1 are now available. 3.7.0rc1 is the final planned release preview of Python 3.7, the next feature release of Python. 3.6.6rc1 is the the release preview of the next maintenance release of Python 3.6, the current release of Python. Assuming no critical problems are found prior to *2018-06-27*, the scheduled release dates for 3.7.0 and 3.6.6, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new features and bug fixes in 3.7.0 and 3.6.6 and to prepare your projects to support them. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. Attention macOS users: there is now a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant will become the default version when 3.7.0 releases. Check it out! You can find these releases and more information here: https://www.python.org/downloads/release/python-370rc1/ https://www.python.org/downloads/release/python-366rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0b5 bonus beta!
A 3.7 update: Python 3.7.0b5 is now the final beta preview of Python 3.7, the next feature release of Python. 3.7.0b4 was intended to be the final beta but, due to some unexpected compatibility issues discovered during beta testing of third-party packages, we decided to revert some changes in how Python's 3.7 Abstract Syntax Tree parser deals with docstrings; 3.7.0b5 now behaves like 3.6.x and previous releases (refer to the 3.7.0b5 changelog for more information). **If your code makes use of the ast module, you are strongly encouraged to test (or retest) that code with 3.7.0b5, especially if you previously made changes to work with earlier preview versons of 3.7.0.** As always, please report issues found to bugs.python.org as soon as possible. Please keep in mind that this is a preview release and its use is not recommended for production environments. Attention macOS users: there is now a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out! The next (and final, we hope!) preview release will be the release candidate which is now planned for 2018-06-11, followed by the official release of 3.7.0, now planned for 2018-06-27. You can find Python 3.7.0b5 and more information here: https://www.python.org/downloads/release/python-370b5/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0b4, final 3.7 beta, now available for testing
Python 3.7.0b4 is the final beta preview of Python 3.7, the next feature release of Python. Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare your projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. Attention macOS users: there is now a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out! The next preview release will be the release candidate and is planned for 2018-05-21 followed by the official release of 3.7.0, planned for 2018-06-15. You can find Python 3.7.0b4 and more information here: https://www.python.org/downloads/release/python-370b4/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0b3 is now available for testing
On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b3. b3 is the third of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You can find Python 3.7.0b3 here: https://www.python.org/downloads/release/python-370b3/ Among the new major new features in Python 3.7 are: * PEP 538, Coercing the legacy C locale to a UTF-8 based locale * PEP 539, A New C-API for Thread-Local Storage in CPython * PEP 540, UTF-8 mode * PEP 552, Deterministic pyc * PEP 553, Built-in breakpoint() * PEP 557, Data Classes * PEP 560, Core support for typing module and generic types * PEP 562, Module __getattr__ and __dir__ * PEP 563, Postponed Evaluation of Annotations * PEP 564, Time functions with nanosecond resolution * PEP 565, Show DeprecationWarning in __main__ * PEP 567, Context Variables Please see "What’s New In Python 3.7" for more information. Additional documentation for these features and for other changes will be provided during the beta phase. https://docs.python.org/3.7/whatsnew/3.7.html Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to https://bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2018-05-21). Our goal is have no ABI changes after beta 3 and no code changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.7 as possible during the beta phase. Attention macOS users: there is a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out! We welcome your feedback. As of 3.7.0b3, the legacy 10.6+ installer also includes a built-in Tcl/Tk 8.6. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next planned release of Python 3.7 will be 3.7.0b4, currently scheduled for 2018-04-30. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0537/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.5 is now available
Python 3.6.5 is now available. 3.6.5 is the fifth maintenance release of Python 3.6, which was initially released in 2016-12 to great interest. Detailed information about the changes made in 3.6.5 can be found in its change log. You can find Python 3.6.5 and more information here: https://www.python.org/downloads/release/python-365/ See the "What’s New In Python 3.6" document for more information about features included in the 3.6 series. Detailed information about the changes made in 3.6.5 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-5-final Attention macOS users: as of 3.6.5, there is a new additional installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default variant in future releases. Check it out! The next maintenance release is expected to follow in about 3 months, around the end of 2018-06. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation: https://www.python.org/psf/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: macOS specific - reading calendar information
On 2018-03-15 03:58, Christian Gollwitzer wrote: > Am 15.03.18 um 08:32 schrieb Jan Erik Moström: >> I would like to read what calendar events I have on a range of days. I >> would like to get the data from whatever storage Calendar use, in my >> personal case I sync to iCloud. [...] > The native script language is Apple Script or JavaScript. If you want to > control it from Python, you need a bridge. I have no experience with it, > but a quick Google search reveals > https://pypi.python.org/pypi/py-applescript and > https://docs.python.org/2/library/macosa.html py-appscript was a great tool but is no longer maintained by its developer because Apple deprecated much of the interfaces it was built on. It still might be useful in this case. At a lower level, the PyObjC project provides bridging between Python and Objective C and provides Python wrappers for many macOS system frameworks, include the CalendarStore framework. https://pypi.python.org/pypi/pyobjc -- https://mail.python.org/mailman/listinfo/python-list
Re: urllib.request.urlopen fails with https
On 2018-03-14 18:04, Irv Kalb wrote: > File > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", > line 1320, in do_open > raise URLError(err) > urllib.error.URLError: certificate verify failed (_ssl.c:749)> If you are using Python 3.6 for macOS from a python.org installer, did you follow the instructions displayed in the installer ReadMe and also saved at: /Applications/Python 3.6/ReadMe.rtf to run the "Install Certificates.command" ? Either double-click on it in the Finder or, from a shell command line, type: open "/Applications/Python 3.6/Install Certificates.command" Certificate verification and OpenSSL **NEW** This variant of Python 3.6 now includes its own private copy of OpenSSL 1.0.2. Unlike previous releases, the deprecated Apple-supplied OpenSSL libraries are no longer used. This also means that the trust certificates in system and user keychains managed by the Keychain Access application and the security command line utility are no longer used as defaults by the Python ssl module. For 3.6.0, a sample command script is included in /Applications/Python 3.6 to install a curated bundle of default root certificates from the third-party certifi package (https://pypi.python.org/pypi/certifi). If you choose to use certifi, you should consider subscribing to the project's email update service to be notified when the certificate bundle is updated. -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.5rc1 is now available for testing
Announcing the immediate availability of Python 3.6.5 release candidate 1! Python 3.6.5rc1 is the first release candidate for Python 3.6.5, the next maintenance release of Python 3.6. While 3.6.5rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). 3.6.5 is planned for final release on 2018-03-26 with the next maintenance release expected to follow in about 3 months. You can find Python 3.6.5rc1 and more information here: https://www.python.org/downloads/release/python-365rc1/ Attention macOS users: as of 3.6.5rc1, there is a new additional installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default variant in future releases. Check it out! -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0b2 is now available for testing
On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b2. b2 is the second of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You can find Python 3.7.0b2 here: https://www.python.org/downloads/release/python-370b2/ Among the new major new features in Python 3.7 are: * PEP 538, Coercing the legacy C locale to a UTF-8 based locale * PEP 539, A New C-API for Thread-Local Storage in CPython * PEP 540, UTF-8 mode * PEP 552, Deterministic pyc * PEP 553, Built-in breakpoint() * PEP 557, Data Classes * PEP 560, Core support for typing module and generic types * PEP 562, Module __getattr__ and __dir__ * PEP 563, Postponed Evaluation of Annotations * PEP 564, Time functions with nanosecond resolution * PEP 565, Show DeprecationWarning in __main__ * PEP 567, Context Variables Please see "What’s New In Python 3.7" for more information. Additional documentation for these features and for other changes will be provided during the beta phase. https://docs.python.org/3.7/whatsnew/3.7.html Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to https://bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2018-05-21). Our goal is have no ABI changes after beta 3 and no code changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.7 as possible during the beta phase. Attention macOS users: as of b1, there is a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out! We welcome your feedback. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next planned release of Python 3.7 will be 3.7.0b3, currently scheduled for 2018-03-26. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0537/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0b1 is now available for testing
On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b1. b1 is the first of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You can find Python 3.7.0b1 here: https://www.python.org/downloads/release/python-370b1/ Among the new major new features in Python 3.7 are: * PEP 538, Coercing the legacy C locale to a UTF-8 based locale * PEP 539, A New C-API for Thread-Local Storage in CPython * PEP 540, UTF-8 mode * PEP 552, Deterministic pyc * PEP 553, Built-in breakpoint() * PEP 557, Data Classes * PEP 560, Core support for typing module and generic types * PEP 562, Module __getattr__ and __dir__ * PEP 563, Postponed Evaluation of Annotations * PEP 564, Time functions with nanosecond resolution * PEP 565, Show DeprecationWarning in __main__ * PEP 567, Context Variables Please see "What’s New In Python 3.7" for more information. Additional documentation for these features and for other changes will be provided during the beta phase. https://docs.python.org/3.7/whatsnew/3.7.html Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to https://bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2018-05-21). Our goal is have no ABI changes after beta 3 and no code changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.7 as possible during the beta phase. Attention macOS users: with 3.7.0b1, we are providing a choice of two binary installers. The new variant provides a 64-bit-only version for macOS 10.9 and later systems; this variant also now includes its own built-in version of Tcl/Tk 8.6. We welcome your feedback. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next planned release of Python 3.7 will be 3.7.0b2, currently scheduled for 2018-02-26. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0537/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0a4 is now available for testing
Python 3.7.0a4 is the last of four planned alpha releases of Python 3.7, the next feature release of Python. During the alpha phase, Python 3.7 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview release, 3.7.0b1, is planned for 2018-01-29. You can find Python 3.7.0a4 and more information here: https://www.python.org/downloads/release/python-370a4/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.4 is now available
On behalf of the Python development community and the Python 3.6 release team, I am happy to announce the availability of Python 3.6.4, the fourth maintenance release of Python 3.6. Detailed information about the changes made in 3.6.4 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-4-final Please see "What’s New In Python 3.6" for more information about the new features in Python 3.6: https://docs.python.org/3.6/whatsnew/3.6.html You can download Python 3.6.4 here: https://www.python.org/downloads/release/python-364/ The next maintenance release of Python 3.6 is expected to follow in about 3 months, around the end of 2018-03. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ Enjoy! -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.4rc1 and 3.7.0a3 now available for testing
Announcing the immediate availability of Python 3.6.4 release candidate 1 and of Python 3.7.0 alpha 3! Python 3.6.4rc1 is the first release candidate for Python 3.6.4, the next maintenance release of Python 3.6. While 3.6.4rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). 3.6.4 is planned for final release on 2017-12-18 with the next maintenance release expected to follow in about 3 months. You can find Python 3.6.4rc1 and more information here: https://www.python.org/downloads/release/python-364rc1/ Python 3.7.0a3 is the third of four planned alpha releases of Python 3.7, the next feature release of Python. During the alpha phase, Python 3.7 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview release, 3.7.0a4, is planned for 2018-01-08. You can find Python 3.7.0a3 and more information here: https://www.python.org/downloads/release/python-370a3/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: [Python-Dev] [RELEASE] Python 3.6.4rc1 and 3.7.0a3 now available for testing
On Dec 6, 2017, at 07:30, Steve Holden wrote: > In your role as a representative of the many fine release managers Python has > had over the years I'd like to thank you for continuing to make high-quality > software available to a large and growing community. And thanks to everyone > who contributes to Python so the majority just get to enjoy it. Thank you for your kind words, Steve, but, as you know, in our roles as release managers, we are just the conductors, making sure that the release trains get scheduled and arrive at their station stops on time. Without the enormous contributions of all core developers and an increasing body of other contributors, all volunteering their time, the trains would be empty. For those of you who might be tempted to contribute your time to working on Python, feel free to hop on board: https://devguide.python.org. Or if you or perhaps your organization would like to help the Python community in other ways, consider supporting the Python Software Foundation: https://www.python.org/psf-landing/. -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.4rc1 and 3.7.0a3 now available for testing
Announcing the immediate availability of Python 3.6.4 release candidate 1 and of Python 3.7.0 alpha 3! Python 3.6.4rc1 is the first release candidate for Python 3.6.4, the next maintenance release of Python 3.6. While 3.6.4rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). 3.6.4 is planned for final release on 2017-12-18 with the next maintenance release expected to follow in about 3 months. You can find Python 3.6.4rc1 and more information here: https://www.python.org/downloads/release/python-364rc1/ Python 3.7.0a3 is the third of four planned alpha releases of Python 3.7, the next feature release of Python. During the alpha phase, Python 3.7 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview release, 3.7.0a4, is planned for 2018-01-08. You can find Python 3.7.0a3 and more information here: https://www.python.org/downloads/release/python-370a3/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.7.0a2 is now available for testing
Python 3.7.0a2 is the second of four planned alpha previews of Python 3.7, the next feature release of Python. During the alpha phase, Python 3.7 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview, 3.7.0a3, is planned for 2017-11-27. You can find Python 3.7.0a2 and more information here: https://www.python.org/downloads/release/python-370a2/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.3 is now available
On behalf of the Python development community and the Python 3.6 release team, I am happy to announce the availability of Python 3.6.3, the third maintenance release of Python 3.6. Detailed information about the changes made in 3.6.3 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-3-final Please see "What’s New In Python 3.6" for more information about the new features in Python 3.6: https://docs.python.org/3.6/whatsnew/3.6.html You can download Python 3.6.3 here: https://www.python.org/downloads/release/python-363/ The next maintenance release of Python 3.6 is expected to follow in about 3 months, around the end of 2017-12. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ Enjoy! -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.3rc1 and 3.7.0a1 are now available for testing and more
The Python build factories have been busy the last several weeks preparing our fall lineup of releases. Today we are happy to announce three additions: 3.6.3rc1, 3.7.0a1, and 3.3.7 final, which join last weekend's 2.7.14 and last month's 3.5.4 bug-fix releases and 3.4.7 security-fix update (https://www.python.org/downloads/). 1. Python 3.6.3rc1 is the first release candidate for Python 3.6.3, the next maintenance release of Python 3.6. While 3.6.3rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). 3.6.3 is planned for final release on 2017-10-02 with the next maintenance release expected to follow in about 3 months. You can find Python 3.6.3rc1 and more information here: https://www.python.org/downloads/release/python-363rc1/ 2. Python 3.7.0a1 is the first of four planned alpha releases of Python 3.7, the next feature release of Python. During the alpha phase, Python 3.7 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview release, 3.6.0a2, is planned for 2017-10-16. You can find Python 3.7.0a1 and more information here: https://www.python.org/downloads/release/python-370a1/ 3. Python 3.3.7 is also now available. It is a security-fix source-only release and is expected to be the final release of any kind for Python 3.3.x before it reaches end-of-life status on 2017-09-29, five years after its initial release. Because 3.3.x has long been in security-fix mode, 3.3.7 may no longer build correctly on all current operating system releases and some tests may fail. If you are still using Python 3.3.x, we **strongly** encourage you to upgrade now to a more recent, fully supported version of Python 3. You can find Python 3.3.7 here: https://www.python.org/downloads/release/python-337/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Python 3.3.7rc1 now available prior to Python 3.3 end-of-life
On behalf of the Python development community and the Python 3.3 release teams, I would like to announce the availability of Python 3.3.7rc1, the release candidate of Python 3.3.7. It is a security-fix source-only release. Python 3.3.0 was released 5 years ago on 2012-09-29 and has been in security-fix-only mode since 2014-03-08. Per project policy, all support for the 3.3 series of releases ends on 2017-09-29, five years after the initial release. Therefore, Python 3.3.7 is expected to be the final release of any kind for the 3.3 series. After 2017-09-29, **we will no longer accept bug reports nor provide fixes of any kind for Python 3.3.x**; of course, third-party distributors of Python 3.3.x may choose to offer their own extended support. Because 3.3.x has long been in security-fix mode, 3.3.7 may no longer build correctly on all current operating system releases and some tests may fail. If you are still using Python 3.3.x, we **strongly** encourage you to upgrade to a more recent, fully supported version of Python 3; see https://www.python.org/downloads/. If you are still using your own build of Python 3.3.x , please report any critical issues with 3.3.7rc1 to the Python bug tracker prior to 2017-09-18, the expected release date for Python 3.3.7 final. Even better, use the time to upgrade to Python 3.6.x! Thank you to everyone who has contributed to the success of Python 3.3.x over the past years! You can find Python 3.3.7rc1 here: https://www.python.org/downloads/release/python-337rc1/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.2 is now available
On behalf of the Python development community and the Python 3.6 release team, I am happy to announce the availability of Python 3.6.2, the second maintenance release of Python 3.6. 3.6.0 was released on 2016-12-22 to great interest and we are now providing the second set of bugfixes and documentation updates for it; the first maintenance release, 3.6.1, was released on 2017-03-31. Detailed information about the changes made in 3.6.2 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-2 Please see "What’s New In Python 3.6" for more information about the new features in Python 3.6: https://docs.python.org/3.6/whatsnew/3.6.html You can download Python 3.6.2 here: https://www.python.org/downloads/release/python-362/ The next maintenance release of Python 3.6 is expected to follow in about 3 months, around the end of 2017-09. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ Enjoy! P.S. If you need to download the documentation set for 3.6.2 immediately, you can always find the release version here: https://docs.python.org/release/3.6.2/download.html The most current updated versions will appear here: https://docs.python.org/3.6/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.2rc2 is now available for testing
On behalf of the Python development community and the Python 3.6 release team, I would like to announce the availability of Python 3.6.2rc2. 3.6.2rc2 is the second release candidate for Python 3.6.2, the next maintenance release of Python 3.6. 3.6.2rc2 includes fixes for three security-related issues resolved since the previous release candidate; see the change log (link below). While 3.6.2rc2 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.2rc2 here: https://www.python.org/downloads/release/python-362rc2/ and its change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-2-release-candidate-2 3.6.2 is now planned for final release on 2017-07-17 with the next maintenance release expected to follow in about 3 months. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.2rc1 is now available for testing
On behalf of the Python development community and the Python 3.6 release team, I would like to announce the availability of Python 3.6.2rc1. 3.6.2rc1 is the first release candidate for Python 3.6.2, the next maintenance release of Python 3.6. While 3.6.2rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.2rc1 here: https://www.python.org/downloads/release/python-362rc1/ and its change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-2-release-candidate-1 3.6.2 is planned for final release on 2017-06-30 with the next maintenance release expected to follow in about 3 months. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.1 is now available
On behalf of the Python development community and the Python 3.6 release team, I would like to announce the availability of Python 3.6.1, the first maintenance release of Python 3.6. 3.6.0 was released on 2016-12-22 to great interest and now, three months later, we are providing the first set of bugfixes and documentation updates for it. Although it should be transparent to users of Python, 3.6.1 is the first release after some major changes to our development process so we ask users who build Python from source to be on the lookout for any unexpected differences. Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.1 here: https://www.python.org/downloads/release/python-361/ and its change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-1 The next maintenance release of Python 3.6 is expected to follow in about 3 months by the end of 2017-06. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.1rc1 is now available
On behalf of the Python development community and the Python 3.6 release team, I would like to announce the availability of Python 3.6.1rc1. 3.6.1rc1 is the first release candidate for Python 3.6.1, the first maintenance release of Python 3.6. 3.6.0 was released on 2017-12-22 to great interest and now, three months later, we are providing the first set of bugfixes and documentation updates for it. While 3.6.1rc1 is a preview release and, thus, not intended for production environments, we encourage you to explore it and provide feedback via the Python bug tracker (https://bugs.python.org). Although it should be transparent to users of Python, 3.6.1 is the first release after some major changes to our development process so we ask users who build Python from source to be on the lookout for any unexpected differences. 3.6.1 is planned for final release on 2017-03-20 with the next maintenance release expected to follow in about 3 months. Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.1rc1 here: https://www.python.org/downloads/release/python-361rc1/ More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0 is released!
On behalf of the Python development community and the Python 3.6 release team, I am pleased to announce the availability of Python 3.6.0. Python 3.6.0 is the newest major release of the Python language, and it contains many new features and optimizations. See the "What’s New In Python 3.6" document for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can download Python 3.6.0 here: https://www.python.org/downloads/release/python-360/ Also, most third-party distributors of Python should be making 3.6.0 packages available soon. Maintenance releases for the 3.6 series will follow at regular intervals starting in the first quarter of 2017. We hope you enjoy Python 3.6.0! P.S. As a volunteer-staffed open source project, we could not bring Python releases to you without the enormous contributions of many, many people. Thank you to all who have contributed and reviewed code and documentation changes, documented and investigated bugs, tested Python and third-party packages, and provided and supported the infrastructure needed to support Python development and testing. Please consider supporting the work of the Python Software Foundation. More at: https://www.python.org/psf-landing/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0rc2 is now available
On behalf of the Python development community and the Python 3.6 release team, I would like to announce the availability of Python 3.6.0rc2. 3.6.0rc2 is the second release candidate for Python 3.6, the next major release of Python. Code for 3.6.0 is now frozen. 3.6.0rc2 is the same code base as the first release candidate, 3.6.0rc1, with the addition of fixes for a couple of critical problems and with some documentation additions and updates. Assuming no further release critical problems are found prior to the 3.6.0 final release date, now planned for 2016-12-23, the 3.6.0 final release will be the same code base as this 3.6.0rc2. Maintenance releases for the 3.6 series will follow at regular intervals starting in the first quarter of 2017. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 * PEP 529 - Change Windows filesystem encoding to UTF-8 * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0rc2 here: https://www.python.org/downloads/release/python-360rc2/ Note that 3.6.0rc2 is still a preview release and thus its use is not recommended for production environments. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0rc1 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm excited to announce the availability of Python 3.6.0rc1. 3.6.0rc1 is the release candiate for Python 3.6, the next major release of Python. Code for 3.6.0 is now frozen. Assuming no release critical problems are found prior to the 3.6.0 final release date, currently 2016-12-16, the 3.6.0 final release will be the same code base as this 3.6.0rc1. Maintenance releases for the 3.6 series will follow at regular intervals starting in the first quarter of 2017. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 * PEP 529 - Change Windows filesystem encoding to UTF-8 * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0rc1 here: https://www.python.org/downloads/release/python-360rc1/ Note that 3.6.0rc1 is still a preview release and thus its use is not recommended for production environments. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0b4 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm pleased to announce the availability of Python 3.6.0b4. 3.6.0b4 is the last planned beta release of Python 3.6, the next major release of Python. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 * PEP 529 - Change Windows filesystem encoding to UTF-8 * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0b4 here: https://www.python.org/downloads/release/python-360b4/ Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2016-12-05). Our goal is have no changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments The next pre-release of Python 3.6 will be 3.6.0rc1, the release candidate, currently scheduled for 2016-12-05. The official release of Python 3.6.0 is currently scheduled for 2016-12-16. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0b3 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm pleased to announce the availability of Python 3.6.0b3. 3.6.0b3 is the third of four planned beta releases of Python 3.6, the next major release of Python. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 (provisional) * PEP 529 - Change Windows filesystem encoding to UTF-8 (provisional) * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0b3 here: https://www.python.org/downloads/release/python-360b3/ Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2016-12-05). Our goal is have no changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments The next pre-release of Python 3.6 will be 3.6.0b4, currently scheduled for 2016-11-21. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0b2 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0b2. 3.6.0b2 is the second of four planned beta releases of Python 3.6, the next major release of Python, and marks the end of the feature development phase for 3.6. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 (provisional) * PEP 529 - Change Windows filesystem encoding to UTF-8 (provisional) * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0b2 here: https://www.python.org/downloads/release/python-360b2/ Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2016-12-05). Our goal is have no changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments The next planned release of Python 3.6 will be 3.6.0b3, currently scheduled for 2016-10-31. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: Copying a compiled Python from one system to another
On 2016-10-06 11:04, Steve D'Aprano wrote: > On Fri, 7 Oct 2016 01:36 am, Ned Deily wrote: >> On 2016-10-02 00:25, Steve D'Aprano wrote: >>> On Sun, 2 Oct 2016 01:58 pm, Chris Angelico wrote: >>>> Hmm, I've possibly missed something here, which may indicate a >>>> problem. Why can't your existing machines build? Is it because they >>>> have too-old versions of tools, and if so, which? >>> Yes, this. You need gcc 4.8 or better to build CPython 3.6, and the most >>> recent any of my systems support is 4.4. >> >> I'm using a gcc 4.2 to build 3.6. > > How on earth do you do that? What magic incantations are you using? > > I understand that Python 3.6 is now using C99 features that aren't available > before gcc 4.8. 3.6 is only using a subset of the C99 features that were proposed in the earlier python-dev discussion. In this case, I am using the Apple version of GNU gcc-4.2 that shipped with Xcode 3 on OS X 10.5 and 10.6. I haven't tried it with other versions of gcc-4.2 but it's worth trying. -- https://mail.python.org/mailman/listinfo/python-list
Re: Copying a compiled Python from one system to another
On 2016-10-02 00:25, Steve D'Aprano wrote: > On Sun, 2 Oct 2016 01:58 pm, Chris Angelico wrote: >> Hmm, I've possibly missed something here, which may indicate a >> problem. Why can't your existing machines build? Is it because they >> have too-old versions of tools, and if so, which? > Yes, this. You need gcc 4.8 or better to build CPython 3.6, and the most > recent any of my systems support is 4.4. I'm using a gcc 4.2 to build 3.6. -- https://mail.python.org/mailman/listinfo/python-list
Re: Getting IDLE to use correct Tcl/Tk on MacOSX 10.6?
On 2016-09-27 18:47, Gregory Ewing wrote: > I don't normally use IDLE, but I had occasion to use it > on MacOSX 10.6 to answer someone's question, and of course > it didn't work properly due to Apple's broken Tcl/Tk. > > I followed the advice to install ActiveState Tcl 8.5.18.0, > but my Python still wants to use Apple's Tcl. > > How do I persuade Python to use the new one I've installed? > It's a framework install of Python 3.5 that I compiled > myself. Do I need to rebuild it to get it to pick up the > right Tcl? Or is there an environment variable I can set? As you probably know, on OS X the dynamic load library paths linked into executables and the like are normally absolute paths. This applies to _tkinter.so. You can check the path with otool -L. $ python3.5 -c "import _tkinter; print(_tkinter.__file__)" /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/lib-dynload/_tkinter.cpython-35m-darwin.so $ otool -L $(python3.5 -c "import _tkinter; print(_tkinter.__file__)") /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/lib-dynload/_tkinter.cpython-35m-darwin.so: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl (compatibility version 8.5.0, current version 8.5.18) /Library/Frameworks/Tk.framework/Versions/8.5/Tk (compatibility version 8.5.0, current version 8.5.18) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0) The ActiveState Tcl/Tk frameworks are installed in /Library/Frameworks; your _tkinter was linked with the Apple-supplied versions in /System/Library/Frameworks. If you rebuild _tkinter after the new versions are in /Library/Frameworks, everything should be just fine, since, by default, /Library/Frameworks is searched at link time before /System/Library/Frameworks. You could also override the search order at run time for all frameworks with: DYLD_FRAMEWORK_PATH=/Library/Frameworks See man dyld for more info. Or you might be able to use install_name_tool to modify the path to the framework. -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0b1 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0b1. 3.6.0b1 is the first of four planned beta releases of Python 3.6, the next major release of Python, and marks the end of the feature development phase for 3.6. Among the new major new features in Python 3.6 are: * PEP 468 - Preserving the order of **kwargs in a function * PEP 487 - Simpler customization of class creation * PEP 495 - Local Time Disambiguation * PEP 498 - Literal String Formatting * PEP 506 - Adding A Secrets Module To The Standard Library * PEP 509 - Add a private version to dict * PEP 515 - Underscores in Numeric Literals * PEP 519 - Adding a file system path protocol * PEP 520 - Preserving Class Attribute Definition Order * PEP 523 - Adding a frame evaluation API to CPython * PEP 524 - Make os.urandom() blocking on Linux (during system startup) * PEP 525 - Asynchronous Generators (provisional) * PEP 526 - Syntax for Variable Annotations (provisional) * PEP 528 - Change Windows console encoding to UTF-8 (provisional) * PEP 529 - Change Windows filesystem encoding to UTF-8 (provisional) * PEP 530 - Asynchronous Comprehensions Please see "What’s New In Python 3.6" for more information: https://docs.python.org/3.6/whatsnew/3.6.html You can find Python 3.6.0b1 here: https://www.python.org/downloads/release/python-360b1/ Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2016-12-05). Our goal is have no changes after rc1. To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments The next planned release of Python 3.6 will be 3.6.0b2, currently scheduled for 2016-10-03. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
{RELEASE] Python 3.6.0a4 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a4. 3.6.0a4 is the last of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. You can find Python 3.6.0a4 here: https://www.python.org/downloads/release/python-360a4/ The next planned release of Python 3.6 will be 3.6.0b1, currently scheduled for 2016-09-12. 3.6.0b1 will mark the beginning of the beta phase of Python 3.6; at that time, feature development for 3.6 will be complete and the emphasis will change to fixing bugs and regressions. More information about the release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ --Ned -- Ned Deily n...@python.org -- [] signature.asc Description: OpenPGP digital signature -- https://mail.python.org/mailman/listinfo/python-list
Re: Tcl/Tk for Python 3.6.0a3 on Os X 10.9.5
On 2016-08-02 15:08, Terry Reedy wrote: > On 8/2/2016 4:21 AM, munozvvale...@gmail.com wrote: >> I am new to the programming world but I need to learn this program >> for a research class that I am taking. I have downloaded Python >> 3.6.0a3 on a Mac 10.9.5 and realized that I also need to download an >> Active Tcl for it. I can't find one for this version. Can someone >> please direct me to it? The most recent one I've been able to find is >> for Python 3.5.2 > This page https://www.python.org/download/mac/tcltk/ > does not yet mention 3.6. So I would start with the recommendation for > 3.5.2: tcl/tk 8.5.18. Yes, sorry, I don't usually update that page for pre-releases. The information you need is also included in the python.org OS X installer Read Me file which is displayed during the installation process. (A copy of it is also preserved at "/Applications/Python 3.6/ReadMe.rtf".). In the section "Update your version of Tcl/Tk to use IDLE or other Tk applications": "For the initial alpha releases of Python 3.6, the installer is linked with Tcl/Tk 8.5; this will change prior to the beta releases of 3.6.0." -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.6.0a3 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a3. 3.6.0a3 is the third of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. You can find Python 3.6.0a3 here: https://www.python.org/downloads/release/python-360a3/ The next release of Python 3.6 will be 3.6.0a4, currently scheduled for 2016-08-15. --Ned -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Python 3.6.0a2 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a2. 3.6.0a2 is the first of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. You can find Python 3.6.0a2 here: https://www.python.org/downloads/release/python-360a2/ The next release of Python 3.6 will be 3.6.0a3, currently scheduled for 2016-07-11. Enjoy! --Ned -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Python 3.6.0a1 is now available
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a1. 3.6.0a1 is the first of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. You can find Python 3.6.0a1 here: https://www.python.org/downloads/release/python-360a1/ The next release of Python 3.6 will be 3.6.0a2, currently scheduled for 2016-06-13. Enjoy! --Ned -- Ned Deily n...@python.org -- [] -- https://mail.python.org/mailman/listinfo/python-list
Re: Fixing Python install on the Mac after running 'CleanMyMac' (fwd)
In article , kacyjo...@lclark.edu wrote: > I was having this same problem, entered those commands and got this as a > response: > > MacBook-Pro:~ kacyjones$ /usr/bin/python2.7 -c 'import > numpy;print(numpy.__file__)' > /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/num > py/__init__.pyc > MacBook-Pro:~ kacyjones$ > MacBook-Pro:~ kacyjones$ /usr/bin/python2.7 -c 'import > sys;print(sys.version)' > 2.7.10 (default, Jul 14 2015, 19:46:27) > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] > > Any idea what that means for my system? Since the original reply, Apple has updated the version of the OS X 10.10.x system Python 2.7 to 2.7.10. So that looks good. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: beginners choice: wx or tk?
In article , Kevin Walzer wrote: > On 7/11/15 10:48 AM, Laura Creighton wrote: > > Unless I was misinformed 2 weeks or so ago when I asked, that is the > > problem. Tcl/Tk 8.6 works (and is shipped with) OSX, but tkinter > > and idle don't work with it. We will see what Ned Deily says > > when he gets around to reading this. > > You were misinformed. Tkinter has worked fine with Tk 8.6 for a long > time. The issues with Tk on the Mac, owing to Apple's force migration of > GUI libraries to Cocoa, have finally been more or less resolved, and Tk > 8.6.4 is now quite stable on OS X. I believe Laura is referring to the Pythons installed by python.org installers and it is true that their versions of tkinter and IDLE are not linked with 8.6 (but it is not correct that 8.6 is shipped with OS X). As I replied earlier, the issue is not that Tkinter doesn't work with Tk 8.6 on OS X: as you say, it does. The issues are that (1) Apple doesn't supply 8.6 with OS X; (2) the Pythons supplied by the python.org installers for OS X have traditionally depended on using Apple-supplied Tk's shipped with OS X (with an override to ActiveTcl if installed); (3) Apple has not updated the version of Tk 8.5 shipped with recent releases of OS X, thus still shipping an early version of Cocoa Tk with critical bugs that have been fixed upstream by you (Kevin) and others; (4) while liberally licensed, ActiveTcl is not free or open source software so it is problematic to require all tkinter users to have to install it when using python.org Pythons. The best solution at the moment would be for the python.org OS X installers to supply their own builds of Tcl/Tk (like the python.org Windows installers do). That hasn't happened yet (we tried one approach a while back but ran into problems with some key third-party Python packages expecting files to be in particular locations); I hope to try again in the near future. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: beginners choice: wx or tk?
In article <201507111448.t6bemh6z025...@fido.openend.se>, Laura Creighton wrote: > In a message of Sat, 11 Jul 2015 13:56:09 +0200, Christian Gollwitzer writes: > >Am 11.07.15 um 13:27 schrieb Laura Creighton: > >> Also, if you need your app to work with MacOS, be warned that you > >> will need an older version of tk than the most recent one. > >> This information is current: https://www.python.org/download/mac/tcltk/ > >> Don't use 8.6 > >I'm not sure how recent this really is. Kevin Walzer has done a lot of > >work to get recent Tcl/Tk (i.e. 8.6) running on OSX. The most recent > >ActiveTcl release is 8.6.4.1. I'm using exclusively Tk 8.6 on the Mac > >without problems. > Unless I was misinformed 2 weeks or so ago when I asked, that is the > problem. Tcl/Tk 8.6 works (and is shipped with) OSX, but tkinter > and idle don't work with it. We will see what Ned Deily says > when he gets around to reading this. Apple still does not ship 8.6 with OS X, only 8.5 (as of OS X 10.6) and, for backwards compatibility, 8.4. That's why the python.org Python installers for OS X do not yet use 8.6. ActiveState does provide an OS X installer for Tcl/Tk 8.6 but it is not open source; assuming your use is compatible with their (liberal) license, you can build your own Python linking with it. Also, some third-party package managers for OS X supply a Python linked with their own Tcl/Tk 8.6, e.g. MacPorts. We haven't wanted to get into the business of building and shipping our own Tcl/Tk for python.org OS X installers but, because of Apple's recent poor support for Tcl/Tk, we more or less need to; it's on the list of future enhancements. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Bug in floating point multiplication
In article <559579bb$0$2921$e4fe5...@news.xs4all.nl>, Irmen de Jong wrote: > Tested on Mac OSX 10.10.4, with a 64-bit core2duo processor. Below are all > 64-bit python > implementations: > 2.6.9 (apple supplied), 2.7.6 (apple supplied), 3.4.3 (homebrew), and > pypy-2.6.0 > (homebrew). I don't have any 32 bit Python implementations on the mac. Sure you do! $ /usr/bin/python2.7 -c 'import sys;print(sys.maxsize)' 9223372036854775807 $ arch -i386 /usr/bin/python2.7 -c 'import sys;print(sys.maxsize)' 2147483647 -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: (unknown)
In article <6264c933-0ed4-4055-baad-01b322bb6dd4@Calculus-Fantasticus-2.local>, Scott wrote: > We've been using a simple container implementation of a mathematical relation > (https://simple.wikipedia.org/wiki/Relation_(mathematics)) (i.e. an > invertible M:M mapping) for some time. [...] > Below is a link to an implementation, including an ipython notebook with > light exposition and some canonical examples. We'll also be presenting a > poster at SciPy 2015. Let us know if this, or something like it, seems like a > worthwhile addition to the standard Python distribution. Scott, James: The best place to have a discussion about adding new features to Python is on the python-ideas mailing list: https://mail.python.org/mailman/listinfo/python-ideas -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Detect if specific Python.app instance is already running
In article <6651a781-abe1-4f25-b1f3-1f849776d...@googlegroups.com>, Andrei wrote: > On Monday, June 8, 2015 at 1:08:07 AM UTC+2, Ned Deily wrote: > > In article <11e093d5-b78e-4ac6-9a7f-649cb2c2c...@googlegroups.com>, > > Andrei wrote: > > > Alright, I have had some development in > > > http://stackoverflow.com/questions/30694560/detect-if-specific-python-app- > > > inst > > > ance-is-already-running and can prevent running multiple instances of the > > > same app/script (by lockf), but I still need to identify which Python.app > > > instance is running certain script. I guess it's more Cocoa-related > > > question > > > but I hope someone had same problem with tkinter etc. > > > > Can you give a more complete explanation of the goal, i.e. what you are > > trying to end up with here, rather than the steps you are taking to get > > there? It's not at all clear to me what your goal is and the cumbersome > > steps you find you have to take suggest that you might be going down the > > wrong path. OS X apps usually don't have to resort to such hacks. If > > you haven't already, make sure you have looked at the "Information > > Property List Key Reference" for OS X (and iOS) apps. For instance, key > > LSMultipleInstancesProhibited *might* be useful if you really only want > > to ensure that there is only instance of an app launched. > > > > https://developer.apple.com/library/mac/documentation/General/Reference/I > > nfoPlistKeyReference/Articles/LaunchServicesKeys.html > > > > -- > > Ned Deily > > > Hi Ned, > Thanks for your reply! The problem is a bit tricky as I see it. Multiple > instances of Python.app needs to be run since it may run different tkinter > apps etc. What I need is rather simple: > > 1. start app, mark the instance with tkinter app name > 2. start another one, detect that the same instance is already running and > identify it > 3. focus on the first instance, close the second one > > I have solved it with a lock file and a pid file (I guess I could use just > one file for both jobs, but didn't have time to test it yet). I believe it > could be done without files, i.e. by setting some public attributes on app > instances. I could probably also use OS X key storage for this but it gets > too similar to the file approach and I am not sure if it's any better. > > I may be wrong in my thinking. If so, just let me know :) If you have something that works for you, great! A question that remains is: how are you launching all these apps? You mention tkinter so presumably these are "gui" apps. On OS X, native "gui" apps are expected to be packaged as app bundles and launched via Launch Services, e.g. by double-clicking in the Finder or by /usr/bin/open from the command line. Framework installs of Python cheat a bit and provide a default Python.app bundle buried in the framework and do some trickery when python is started conventionally from the command line (e.g. via something like /usr/local/bin/python) to allow the process to be promoted to a gui app, if necessary, like when using Tk from tkinter. If you need gui apps, the most "Mac-thonic" approach would be to use something like py2app to produce each different app as a unique gui app bundle and then, assuming each app's Info.plist are defined properly, OS X will enforce that only one instance of each app is running at a time. But that works only if they are launched as apps rather than run as scripts from the Python interpreter. Of course, this all may be overkill for what you are trying to do but dynamically modifying app bundles or some such certainly does not sound like a good idea for lots of reasons. In any case, good luck! -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: XCode and Python
In article <90a23bdc-7703-4397-b83a-92718ae10...@googlegroups.com>, Sebastian M Cheung via Python-list wrote: > On Thursday, June 11, 2015 at 11:07:59 PM UTC+1, Sebastian M Cheung wrote: > > For some reason I cannot build now in XCode: > > > > $ xcodebuild -find python > > /Users/sebc/anaconda/bin/python > > > > $python > > Python 2.7.10 |Anaconda 2.2.0 (x86_64)| (default, May 28 2015, 17:04:42) > > [GCC 4.2.1 (Apple Inc. build 5577)] on darwin > > Type "help", "copyright", "credits" or "license" for more information. > > Anaconda is brought to you by Continuum Analytics. > > Please check out: http://continuum.io/thanks and https://binstar.org > > > > But XCode now simply say error > > > > env: python: No such file or directory > > Command > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolcha > > in/usr/bin/clang failed with exit code 127 > > > > I couldn't find anything relating XCode for iPhone related to Python build? > > I am using > > anaconda Python > > Anyone? > Or I need to configure something in Xcode? Wild guess: did you by any chance delete the Apple-supplied system python? What is the result of: $ /usr/bin/python -c 'import sys;print(sys.version)' -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Detect if specific Python.app instance is already running
In article <11e093d5-b78e-4ac6-9a7f-649cb2c2c...@googlegroups.com>, Andrei wrote: > Alright, I have had some development in > http://stackoverflow.com/questions/30694560/detect-if-specific-python-app-inst > ance-is-already-running and can prevent running multiple instances of the > same app/script (by lockf), but I still need to identify which Python.app > instance is running certain script. I guess it's more Cocoa-related question > but I hope someone had same problem with tkinter etc. Can you give a more complete explanation of the goal, i.e. what you are trying to end up with here, rather than the steps you are taking to get there? It's not at all clear to me what your goal is and the cumbersome steps you find you have to take suggest that you might be going down the wrong path. OS X apps usually don't have to resort to such hacks. If you haven't already, make sure you have looked at the "Information Property List Key Reference" for OS X (and iOS) apps. For instance, key LSMultipleInstancesProhibited *might* be useful if you really only want to ensure that there is only instance of an app launched. https://developer.apple.com/library/mac/documentation/General/Reference/I nfoPlistKeyReference/Articles/LaunchServicesKeys.html -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Fixing Python install on the Mac after running 'CleanMyMac'
In article , MrJean1 wrote: > FWIW, I recently upgraded an older MacBook to Mac OS X 10.7.5 and there are 3 > different versions of Python in /System/Library/Frameworks/Python.framework, > see: > > $ ls /System/Library/Frameworks/Python.framework/Versions/ > 2.5 2.6 2.7 Current > > > It is unclear whether MacOS X 10.7.5 installed all four of these Python > versions. The older one(s) may be left over from the previous MacOS X > release on the machine For compatibility with applications linked on older OS X releases, Apple customarily ships more than one version of Python frameworks with OS X. There are actually three versions of the system Python frameworks there: you should see that "Current" is actually a symbolic link to "2.7". All of those versions are shipped as part of OS X 10.7. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Fixing Python install on the Mac after running 'CleanMyMac'
In article
,
Skip Montanaro wrote:
> On Fri, May 29, 2015 at 11:11 AM, Ned Deily wrote:
>
> > Well, she could just download a current Python 2.7.x for OS X from
> > python.org, install it, and see if that solves the problem. That would
> > be likely the easiest thing to do and is unlikely to make matters worse.
> >
>
> Might that appear to work at first, but leave some subtle issues which are
> not at first apparent? I don't know how intertwined Apple's Python instance
> is in the day-to-day operation of the operating system (it certainly seems
> to be on some Linux distros), but it's possible that some Apple-specific
> package isn't available at part of the stock Python 2.7 distribution.
Installing a python.org Python (/usr/local/bin/python*) is independent
of and does not interfere with use of the Apple-supplied system Pythons
(/usr/bin/python*). Apple does ship various third-party Python packages
("distributions") with its system Python, like numpy, but they tend to
be old and outdated versions and there are a few Apple-only packages.
But, should that issue arise, that can be resolved by choosing the right
path (/usr/local/bin vs /usr/bin) or removing /usr/local/bin from $PATH.
The thing is the original message in this thread had this:
> They are getting:
> Utility has encountered a fatal error, and will now terminate. A
> Python runtime could not be located. You may need to install a
> framework build of Python or edit the PyRuntimeLocations array in this
> applications info.plist file. Then there are two oblong circles. One
> says Open Console. The other says Terminate.
But ... I just did what I should have done earlier: googled for that
message. And I find that the message is coming from a py2app-built
application (and it seems I answered the question 3 years ago!):
http://stackoverflow.com/questions/10184974/py2app-is-not-copying-the-pyt
hon-framework-to-the-new-app-while-using-virutalenv
The py2app glue code could be looking for Pythons in various spots
including the system Python. So, let's make sure the system Python is
still working. On the most up-to-date 10.7 Lion system (10.7.5), typing
the following two commands should give results the same as those shown
(->):
/usr/bin/python2.7 -c 'import sys;print(sys.version)'
-> 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)
-> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]
/usr/bin/python2.7 -c 'import numpy;print(numpy.__file__)'
->
/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/pytho
n/numpy/__init__.py
If not, then it really may be necessary to restore system files which,
as I noted before, is most safely and accurately done by following
Apple's directions to restore the system from the recovery partition and
a good backup of user files.
--
Ned Deily,
n...@acm.org
--
https://mail.python.org/mailman/listinfo/python-list
Re: Is it possible to find python34.lib from within Python?
In article <68710660-0f24-403a-8c3d-996c06a26...@googlegroups.com>, Paul Moore wrote: > I want to set up a script to build some C code. I need to link it with > python34.lib, but I'm not sure how to locate that file without hard-coding > it. [...] If you are embedding Python, refer to the "Extending and Embedding" document in the Python documentation set and the description of python-config: https://docs.python.org/3/extending/embedding.html#compiling-and-linking- under-unix-like-systems (Of course, if you are extending Python, Distutils should provide all the necessary flags.) -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Fixing Python install on the Mac after running 'CleanMyMac'
In article <201505290959.t4t9xpdk016...@fido.openend.se>, Laura Creighton wrote: > I asked her to come here, but I fear she is feeling a tad too > embarassed to do that right now. I don't know how to find out > the name of the Utility -- the Error message really does say > 'Utility' -- with no name for it. Apparantly there is some log > file you can go take a look at to find out, but I don't know > what it is ... Well, she could just download a current Python 2.7.x for OS X from python.org, install it, and see if that solves the problem. That would be likely the easiest thing to do and is unlikely to make matters worse. If that doesn't work, restoring files from a backup would be in order, again most likely /Library/Frameworks/Python.framework/*. As others have noted, running third-party apps like CleanMyMac is probably not a good idea, but, even if it is as crappy as its sounds, I would think it unlikely that it would be fooling with the Apple-supplied system Python in /System/Library/Frameworks. If it did though, then the safest approach is to do a full Time Machine or other backup and restore the base system from the recovery partition and use the Migration Assistant to restore user files and settings from the backup. But that's a very long and somewhat risky process so should only be done as a last resort. https://support.apple.com/en-us/HT201314 -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Fixing Python install on the Mac after running 'CleanMyMac'
In article <201505290347.t4t3lyjc006...@fido.openend.se>, Laura Creighton wrote: > webmas...@python.org just got some mail from some poor embarrased > soul who ran this program and broke their Python install. > > They are running Mac OSX 10.7.5 > > They are getting: > > Utility has encountered a fatal error, and will now terminate. A > Python runtime could not be located. You may need to install a > framework build of Python or edit the PyRuntimeLocations array in this > applications info.plist file. Then there are two oblong circles. One > says Open Console. The other says Terminate. > > So https://docs.python.org/2/using/mac.html says: > >The Apple-provided build of Python is installed in >/System/Library/Frameworks/Python.framework and /usr/bin/python, >respectively. You should never modify or delete these, as they are >Apple-controlled and are used by Apple- or third-party software. > > So, I assume this poor soul has done precisely that. > > What do I tell her to do now? It would be helpful to know what utility it is that is encountering the fatal error; that message is not familiar and I suspect it is coming from trying to run some third-party application. It may be that the application was depending on a third-party framework installation of Python (in /Library/Frameworks rather than the system Python in /System/Library/Frameworks), such as provided by the python.org OS X installers, but without knowing more information, like what particular version of Python is needed, it would only be speculation. Perhaps the best thing to do is to suggest the OP to participate directly here or an Apple users' forum like http://apple.stackexchange.com. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: need help with an accessibility prototype
In article <201505230925.t4n9pnz8028...@fido.openend.se>, Laura Creighton wrote: > In a message of Fri, 22 May 2015 23:31:19 -0700, Ned Deily writes: > >Tcl/Tk 8.4 is quite old and no longer maintained; 8.6.x is current, > >although 8.5.x is also still in use. > > > >http://www.tcl.tk/man/tcl8.6/TkCmd/keysyms.htm > > > > Ned Deily, > > n...@acm.org > > Thank you Ned. Old bookmark from when I needed this the last time -- > sorry about that. Do you know if you still need to use 8.5 if you are > on Mac OS? i.e. is this page current? > https://www.python.org/download/mac/tcltk/ Yes, it is current. Apple has not yet shipped a version of 8.6 with OS X, so the Apple-supplied Python in current OS X releases use 8.5; OS X 10.5 and earlier systems shipped only with 8.4. At the moment, the Pythons for OS X provided by python.org installers still use 8.5 for the 10.6+ installers and 10.4 for the 10.5+ installers. Some third-party distributors of Python and Tcl/Tk for OS X are now using 8.6, e.g. MacPorts. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: need help with an accessibility prototype
In article <20150516.t4mmg0in013...@fido.openend.se>, Laura Creighton wrote: > By the way http://www.tcl.tk/man/tcl8.4/TkCmd/keysyms.htm > is a list of all the key symbols it is possible for you to get. > There is no guarantee that any platform actually has any of them, > just, if it is not there don't bother trying to look for it. Tcl/Tk 8.4 is quite old and no longer maintained; 8.6.x is current, although 8.5.x is also still in use. http://www.tcl.tk/man/tcl8.6/TkCmd/keysyms.htm Alas, there are an unfortunately large number of platform differences in Tk behavior across the various platforms it supports, primarily Windows, X11, and OS X. Among other resources, there is a useful wiki page that tries to enumerate keyboard and keyboard modifier differences across platforms: http://wiki.tcl.tk/28331 Also, in addition to effbot's venerable Tkinter documentation, more up-to-date material is available at Mark Roseman's TkDocs website and in his e-book "Modern Tkinter". http://www.tkdocs.com -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Installing Python
In article <4048ad0c-a403-4141-ab8b-5884a0084...@gildawson.com>, Gil Dawson wrote: > Hi-- > > I'm on MacOS 10.6.8, learning to use Amazon Web Services' Simple Storage > Service's Command Line Interface (AWS S3 CLI). > > They say in their documentation that their CLI needs Python version 2.7 or > 3.4. I checked in terminal: > > $ python --version > Python 2.6.1 > > So I ran the python-2.7.9-macosx10.6.pkg downloaded from > https://www.python.org/downloads/ and now... > > $ python --version > Python 2.7.9 > $ aws --version > aws-cli/1.7.22 Python/2.6.1 Darwin/10.8.0 > > ...it seems to me that the AWS CLI thinks it is still using the old version. > > Will this cause problems later? Can it be fixed? I don't have any personal experience using that package but, from the instructions I see on their website, if you followed their instructions to download and install pip, you've installed aws into the system Python (2.6) rather than your new Python 2.7. As of 2.7.9, Pythons installed from python.org now include their own version of pip. What you could try is the following: 1. Uninstall the 2.6 version of aws: sudo pip uninstall aws 2. Install aws with the 2.7 version of pip: python2.7 -m pip install aws In the future, whenever something suggests using "pip" or "sudo pip", just use "python2.7 -m pip" instead to be (more) certain that you are installing to the Python instance you want. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: installing matplotlib
In article <176d49d3-6ff8-4d35-b8ec-647f13250...@googlegroups.com>, Pippo wrote: > I am trying to install matplotlib and I keep getting error: [...] > File > "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/distutils/v > ersion.py", line 343, in _cmp > if self.version < other.version: > TypeError: unorderable types: str() < int() > > any idea? If you are running on OS X 10.10 (Yosemite), try upgrading to a current Python 3.4.x. 3.3.x is no longer supported and was released long before Yosemite was. http://bugs.python.org/issue21811 -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Gpg python installer
In article , leonardo davinci wrote: > I am using Kleopatra(gpg for win) to verify the 3.4.3 python installer, > Windows x86 MSI > > >https://www.python.org/ftp/python/3.4.3/python-3.4.3.msi> > www.python.org <https://www.python.org/ftp/python/3.4.3/python-3.4.3.msi> > /ftp/python/3.4.3/ > <https://www.python.org/ftp/python/3.4.3/python-3.4.3.msi>python-3.4.3.msi > <https://www.python.org/ftp/python/3.4.3/python-3.4.3.msi>>. This file does > not have a email in the digital signature and I am having trouble verifying > the validity of the download. Unfortunately, verifying the PGP signature of release files isn't the most user-friendly process, especially on Windows. The release files from python.org are typically PGP-signed in armored detached signature files, in other words, for each release file (like python-3.4.3.msi) there is a separate signature file with an appended .asc extension (python-3.4.3.msi.asc). If you go to the python.org downloads page (https://www.python.org/downloads/) and click on the release in question, it should take you to the page for the release (https://www.python.org/downloads/release/python-343/). Near the bottom of the page, there is a list of downloadable files and to the right of each one there is a "GPG" column with a "SIG" link for each file. Clicking on the SIG link should download the corresponding signature file (python-3.4.3.msi.asc). I'm not familiar with Kleopatra's interface but normally you'd want to download both the installer file and its asc file to the same directory/folder and then tell the GPG program to verify the asc file. The PGP/GPG program will also need to have access to the public keys of the creators / signers of the downloadable files. You will find them listed near the bottom of the Downloads page (https://www.python.org/downloads/). Independently thereof, the python.org Windows installer files are also signed with a public-key code signing certificate that should be automatically verified by the Windows installer program. (Likewise, for the Mac OS X installer files.) Hope this helps! -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: sys.exec_prefix doesn't seem to reflect --exec-prefix path
In article <548dcac1-fa00-4fc1-81d1-ccae28caf...@googlegroups.com>, Ralph Heinkel wrote: > on my linux box there is a python version 2.7.5 installed in /usr/local. > > Now I want to install the newer version 2.7.9, but in a different directory > to avoid clashes with the current installation. > > What I did was: > > ./configure --prefix /usr/local/Python-2.7.9 --exec-prefix > /usr/local/Python-2.7.9 > make > make install Configure arguments need to be specified with '='. Try instead: ./configure --prefix=/usr/local/Python-2.7.9 And --exec-prefix isn't needed in this case as it defaults to the value of --prefix. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Python 2 to 3 conversion - embrace the pain
In article , John Nagle wrote: >If only that were true. Look what I'm reporting bugs on: > > ssl - a core Python module. I assume you're referring to http://bugs.python.org/issue23476. It seems to me that the issue there was not in Python but due to a shortcoming in OpenSSL itself. When the shortcoming was addressed in the most recent major release of OpenSSL (1.0.2), both Python 2 and 3 were modified to take advantage of the new OpenSSL API option when available. Also you would have seen the same behavior if you upgraded to the current version of Python 2 (2.7.9), since 2.7.9 now has most of the same TLS/SSL support code and best practice defaults that 3.4.3 does. So let's not blame this one on Python 3. > cPickle - a core Python module. http://bugs.python.org/issue23655 No question that this appears to be a serious problem and, while yet unresolved, does appear to be a bug in Python 3 itself. > pymysql - the pure-Python recommended way to talk to MySQL. > bs4/html5parser - a popular parser for HTML5 I'm not in a position to comment on those third-party projects. It's too bad that you ran into problems with them. Any idea if you would have seen similar problems if you had used them with Python 2? In any case, of the two problems noted with Python itself, there is only one that appears to be Python 3 related. That's still not good but I think it would be fairer to ascribe a good chunk of the pain you've experienced to the more common pain of upgrading any major software system that depends on multiple third-party components. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Python 2 to 3 conversion - embrace the pain
In article , John Nagle wrote: >All the bugs I'm discussing reflect forced package > changes or upgrades. None were voluntary on my part. You would have run into the SSL certificate issue if you upgraded your Python 2 instance to the current Python 2.7.9. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Python shell: Arrow keys not working in PuTTY
In article <54ec1360$0$12978$c3e8da3$54964...@news.astraweb.com>, Steven D'Aprano wrote: > Ned Deily wrote: > > With no --prefix= on ./configure, the default install location is to > > /usr/local, so "make install" would install a link at > > /usr/local/bin/python (or python3) and it would only overwrite your > > system Python if the system Python happened to be installed in > > /usr/local/bin/. > Well, I'm not going to say you are wrong, but I can say that on Centos 5 > systems (and presumably that includes Fedora and Red Hat of the equivalent > vintage), if you just run `make install` it overwrites the /usr/bin/python > hard link to /usr/bin/python2.4. I know because I've done it :-( If you're using any current 2.7.x or 3.4.x source tarball (or dev repo) from python.org, it ain't gonna happen. (I'm not going to go back and check all the previous releases but it's been that way for a long time, AFAIK.) If you're using source modified by a distribution, like Centos, RH, or Fedora, all bets are off, of course. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: 'Lite' Databases (Re: sqlite3 and dates)
In article <871tljepea@jester.gateway.pace.com>, Paul Rubin wrote: > Ned Deily writes: > > (though I don't know why anyone would want to fork it). > > Same reason lots of people have forked Postgres. Or you might just want > to customize it. Well, for whatever reason one might have, one can: it's public domain software. > > I imagine that is done as an incentive to help > > finance the on-going development and maintenance of SQLite. > It's a pretty unusual and annoying trick that other projects have not > felt they had to resort to. > > > https://www.sqlite.org/testing.html > > Thanks, that's the page I remember. The TH3 test suite is the > interesting one and you can't get it without paying a lot of $. I > guess there is some semantic quibble possible about whether you pay for > the test suite, or (as they put it) pay for Consortium membership and > then (as a member) get the test suite for free. I don't have any special knowledge of the history or current status of the Consortium but it's not difficult to find information and blog posts about it. It seems like this was an approach Richard Hipp and major users of SQLite took to ensure a sustaining funding model for the project while ensuring its independence. It strikes me as a very reasonable and modest constraint given the immense good that the SQLite project has done for so many other projects over the years. Many other less important projects have foundered for lack of sustained funding. https://www.sqlite.org/consortium.html https://blog.lizardwrangler.com/2008/02/27/the-sqlite-consortium/ > Do you know the situation with the SQL Logic Test (SLT) also mentioned > on that page? No -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: 'Lite' Databases (Re: sqlite3 and dates)
In article <54e7b0da.7060...@stoneleaf.us>, Ethan Furman wrote: > On 02/20/2015 01:17 PM, Paul Rubin wrote: > > > SQLite always seemed bloated (from the embedded NoSQL point of view) and > > fragile to me, and the vendor plays an annoying anti-forking trick, > > which is that the code is released but the developers' test suite is > > secret and proprietary (can be licensed from them for big bucks). > Wow, really? I had just started playing with it, but I don't think I'll > bother now. SQLite is one of the most widely-used, best-documented, best-tested, and well-respected software packages in the world. It is used all over by the place on many different platforms. The code, documentation, and some of the tests are in the public domain, freely usable and forkable by all (though I don't know why anyone would want to fork it). It is true that part of the test suite is only released free to SQLite consortium members. I imagine that is done as an incentive to help finance the on-going development and maintenance of SQLite. http://en.wikipedia.org/wiki/SQLite https://www.sqlite.org/about.html https://www.sqlite.org/testing.html https://www.sqlite.org/copyright.html -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: How to install PIL or PILLOW on OS X Yosemite?
In article , KP wrote: > just upgraded my Mac Mini to Yosemite and have never dabbled in Python on > this OS. > > I see it has Python 2.7.6 installed. > > When I do something like > > from PIL import ImageFont, ImageDraw > > it tells me that it cannot find PIL > > How do I install this on Yosemite? Suggestions: stick with Pillow which is the current, maintained fork of the venerable PIL. Decide whether you want to use Python 3 or Python 2. PIL/Pillow installation on OS X is more involved than on some other platforms because it depends on a number of third-party C libraries that are not shipped by Apple in OS X so you need to find another source for them. Rather than trying to build and install everything yourself or downloading a Pillow or PIL installer, I suggest picking one of the several fine distributors of open source packages for OS X and installing everything you need from them (including an up-to-date Python 2 or 3) and for your future needs beyond Pillow; options include Homebrew, MacPorts, Anaconda, Fink, and others. Once you've installed the base framework for the package manager you choose, installing something like Pillow and all of its dependencies is often just a one-line command. It may take a little while to get used to the quirks of the package manager you choose but, if you are going to use OS X for development with Python or many other languages, that time spent will be repaid many times over. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: building c extensions with setuptools that are not tied to python installed on build machine
In article , Matthew Taylor wrote: > Does this make sense to anyone? I'm still a little new to Python in > general (especially binary packaging), and it seems like this would be > a common problem for any projects with C extensions that need broad > binary distribution. Does anyone have any suggestions? Please take a > look at our setup.py file [4] and tell me if we're doing something > egregiously wrong. Just taking a quick look at your setup.py there shows a quite complicated build, including SWIG. One suggestion: keep in mind that it's normal on OS X for the absolute path of shared libraries and frameworks to be embedded in the linked binaries, including the C (or C++) extension module bundles (.so files) built for Python packages. If any of the .so files or any other binary artifacts (executables, shared libraries) created by your package are linked to the Python interpreter's shared library, that may be why you are getting a mixture of Python instances. One way to check for this is to use: otool -L *.so *.dylib on all of the directories containing linked binaries in your project and check for paths like: /System/Library/Frameworks/Python.framework That would be a link to the Apple-supplied system Python. A link to /Library/Frameworks/Python.framework or some other path would be to a third-party Python like from python.org or Homebrew. Due to differences in how the various Pythons are built and depending on what the C or C++ code is doing, it may not be possible to have one binary wheel that works with different Python instances of the same version. For many simple projects, it does work. You *could* also ask on the PythonMac SIG list. https://mail.python.org/mailman/listinfo/pythonmac-sig -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Wildly OT: pop-up virtual keyboard for Mac or Linux?
In article , Skip Montanaro wrote: > I know this is way off-topic for this group, but I figured if anyone > in the online virtual communities I participate in would know the > answer, the Pythonistas would... Google has so far not been my friend > in this realm. > > One of the things I really like about my Skype keyboard (and likely > other "soft" keyboards on Android) is that when you hold down a "key" > for a brief moment, a little mini keyboard pops up, from which you can > easily choose various accented variants and other symbols. For > instance, If I press and hold the "d" key, I see these choices (ignore > the capitalization of the first letter - my mistake sending a text > message to myself from my phone, and I can't seem to convert it to > lower case): –|õ&d©£ď > > While I'm a touch typist, I almost never use auto-repeat, which is the > "binding" of held keys in most environments (curse you, IBM and your > Selectric!). These days I find my self needing accented characters > much more frequently than key repeat (C-u 2 5 - suffices in Emacs to > bat out 25 hyphens). Being an American with an American keyboard, I > haven't the slightest idea how to type any accented characters or > common symbols using the many modifier keys on my keyboard, and no key > caps display what the various options are. And I'm getting kind of > tired of going to Google and searching for "degree symbol". :-/ > > Is there an X11 or Mac extension/program/app/magic thing which I can > install in either environment to get this kind of functionality? I'm > thinking that if you hold down a key for the auto-repeat interval, > instead of the key repeat thing making all sorts of duplicates, a > little window would pop up over/near the insertion point, which I can > navigate with the arrow keys, then hit RET to accept or ESC (or > similar) to cancel. It need not be perfect. It might (for example) > only work in certain environments (Chrome, Emacs, vim, Firefox). > Anyplace to start. It need even be written in Python (though that > would be cool.) I think that once something like this caught hold, it > would fairly quickly take over from the dark lords of auto-repeat. On OS X, the system provides both a "Character Viewer" (which allows the selection of any Unicode character and a "Keyboard Viewer" (which allows you to see the keyboard key mappings as keys and modifiers are pressed). Both can be enabled from System Preferences (System Preferences -> Keyboard -> Keyboard on current 10.10 systems). As of OS X 10.7 (I believe), there are also now popup menus that appear when various keys are held down that show accented variants of the character (this is similar to what iOS on the iPhone and iPad provide). Unfortunately, this doesn't work with some applicatons that do not use the full built-in text system; the Tk implementations on OS X are such applications so the popups don't work with Tkinter apps like IDLE. Nor does it work with X11 apps. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Matplotlib import error
In article , C Smith wrote: > I had python 2.7.6 installed on OS X yosemite, which has always worked > fine, until I tried to install matplotlib with pip. I got the same > error below and upgraded to 2.7.9, used pip to upgrade all the > packages, but still get the same error. > > >>> import matplotlib > Traceback (most recent call last): > File "", line 1, in > File "/Library/Python/2.7/site-packages/matplotlib/__init__.py", > line 180, in > from matplotlib.cbook import is_string_like > File "/Library/Python/2.7/site-packages/matplotlib/cbook.py", line > 33, in It looks like you have a mixture of packages, some left over from using the system Python 2.7 and, unfortunately, the system Python site-package directory is included at the sys.path search path for other Pythons, like the python.org Pythons. If you plan to just use the Python 2.7.9, go to /Library/Python/2.7/site-packages and rm everything there. Then use the 2.7.9 pip to install matplotlib. It should download and install (to /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack ages) the binary wheels for matplotlib and its dependencies, including numpy, and all just work. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Do you like the current design of python.org?
Just a gentle reminder that any problems seen with or changes desired to the python.org website need to be documented on its issue tracker at https://github.com/python/pythondotorg/issues/. Key players working on it likely are not aware of discussions here. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: ssl error with the python mac binary
In article , Paul Wiseman wrote: > I just gave 2.7.9rc1 a go and seems like it is still linked to the same > version of openssl? Yes, it still is for rc1. Unfortunately, I was not able to get everything done in time for rc1 and I didn't want to hold up rc1's release as there are a lot of other changes that need exposure. The final release installer *will* have the new version of openssl. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: Suds Python 2.4.3 Proxy
In article , Chris Angelico wrote: > It might be worth looking at some actual 2.4 documentation. > Unfortunately that doesn't seem to be hosted on python.org any more > (though I might be wrong), https://python.org/ -> Documentation https://www.python.org/doc/ -> Documentation Releases by Version https://www.python.org/doc/versions/ -> Python 2.4.4 https://docs.python.org/release/2.4.4/ -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: ssl error with the python mac binary
In article , Paul Wiseman wrote: > I'm currently using the installer with py2app to make a distributable > app that targets 10.5+ (including ppc). To save having more than one > build I use this for all downloads. Although I'm starting to consider > making a second 32/64 distributable. Are there many major drawbacks > for distributing this i386/ppc binary for all versions of OSX up 10.9 > and 10.10? For a standalone app, not really. The main difference is that, by using the older 10.5 ABI, a few functions in the os module are not available (if they were implemented first in OS X 10.6 or later) and/or they may work a little differently. AFAIK, the most impactful difference, by far, is the OpenSSL version difference you have run into. Up to now, I don't recall any compatibility problems with 10.5 ABI programs running on later versions of OS X or, for the most part, mixing extension modules compiled to later ABIs with a 10.5 Python, although there might be issues with mixing versions of C++ modules (Python and its standard library do not use C++ themselves). But, of course, there's no guarantee that something won't break in a future release of OS X. So far, so good. > That's great news! Thanks for this! I've always found building things > on mac a huge pain and wasn't much looking forward to the prospect of > trying to build a 32/ppc python build on a 64 bit 10.10 machine (would > that even be possible?). It's possible: I do it. But I cheat a bit: I have 10.5 running in a virtual machine on a 10.10 host. In theory, it's possible to build natively on 10.10. The trick is getting a version of Xcode 3 installed on 10.10 since support for building ppc archs was removed in Xcode 4. I also cheat a bit there: I happen to still have copies of Xcode 3.1.4 and 3.2.6 installed on 10.10 because I made sure to preserve them through upgrades from 10.6 days. IIRC, directly installing the necessary components from 3.2.6 on newer systems would require some hacking. Then you have to be really vigilant that the build never strays from the old SDK and tools, which is not something we claim to support at the moment. The VM approach is quite safe and reliable. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
Re: ssl error with the python mac binary
In article , Paul Wiseman wrote: > I've been using the latest mac ppc/i386 binaries from python.org > (https://www.python.org/ftp/python/2.7.8/python-2.7.8-macosx10.5.dmg). > From what I can tell this version is linked against a pretty old > version of OpenSSL (OpenSSL 0.9.7l 28 Sep 2006) which doesn't seem to > be able to handle new sha-256 certificates. > > For example I'm unable to use pip (I guess the certificate was updated > recently) Yes, the current python.org certificate does seem to cause problems for that version of OpenSSL, unfortunately. > Am I right in thinking this is an issue with the build of python > itself? Is there a way I can upgrade the version of OpenSSL linked > with python- or force the python build to look elsewhere for the > library? Or will I have to build my own from source? In the Pythons from the python.org OS X installers, the Python _ssl and _hashlib extension modules are dynamically linked with the system-supplied OpenSSL libraries. If actually running on OS X 10.5, one would have to rebuild _ssl.so and _hashlib.so, linking them with a locally-supplied version of a newer OpenSSL, since different versions of OpenSSL are not ABI-compatible, e.g. 0.9.7 vs 0.9.8 vs 1.0.1. If running on OS X 10.6 or later, another option might be to install from the 64-bit/32-bit installer which is a good idea to do anyway. For pip usage, a workaround would be to manually download distributions from PyPI (or elsewhere) using a web browser and then use pip to install from the downloaded file. The next version of pip is expected to have a --no-check-certificate option that bypasses the certificate check at the cost of reduced security. For the upcoming Python 2.7.9 release (planned for early December), I intend to have the Pythons in the python.org OS X installers use their own versions of OpenSSL and thus no longer depend on the now-deprecated system OpenSSL. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list
