[Python-Dev] macOS: minimum supported version?
Hi, Ned Deily closed old bugs reported on the macOS Tiger buildbot, since this buildbot has been retired 3 months ago (the builders are still visible online, but last builds were 3 months ago). It seems like the oldest macOS buildbot is now macOS El Capitan (macOS 10.11, 2015). Does it mean that the minimum officially supported macOS version is now macOS 10.11 El Capitain? For me, to get an official "full" support, we need a buildbot. Without buildbot, we can only provide a weaker "best-effort" support. Otherwise, the risk of regression is too high. I failed to find any official and obvious list of CPython supported platforms, so I wrote my own list: http://vstinner.readthedocs.io/cpython.html#supported-platforms My first motivation for this list was to get a simple list of supported Windows versions, because I'm unable to follow Windows lifecycle (the PEP 11 has a vague statement about Windows which requires to follow Windows end of life for each Windows release). Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] macOS: minimum supported version?
On May 28, 2018, at 05:05, Victor Stinner wrote: > Ned Deily closed old bugs reported on the macOS Tiger buildbot, since > this buildbot has been retired 3 months ago (the builders are still > visible online, but last builds were 3 months ago). Perhaps Zach or someone else can remove them from the list. > It seems like the oldest macOS buildbot is now macOS El Capitan (macOS > 10.11, 2015). Does it mean that the minimum officially supported macOS > version is now macOS 10.11 El Capitain? One way to answer that question is to look at the macOS versions we support with python.org installers. If you look at the current download pages for current releases, you'll see we provide installers that support macOS versions from 10.6 (Snow Leopard) theough the current 10.13 (High Sierrs) so we definitely support those versions. Earlier versions are supported on a best-effort basis. -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
Hi, Since one or two weeks, I noticed that it's difficult to merge pull requests into the 2.7 branch. If a different commit is pushed in the meanwhile (if a different PR has been merged), the 2.7 branch diverges and the PR is immediately marked as "This branch is out-of-date with the base branch" and the "Squash and Merge" button is disabled (grey). For example my PR https://github.com/python/cpython/pull/7120 which changes Lib/test/regrtest.py cannot be merged because a commit touching the documentation (Doc/ directory) has been merged after I posted my PR and before the CI completed. I don't see the same behavior on the master branch. Is the 2.7 branch configured as more strict? Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
25.05.18 05:09, Jan Claeys пише: On Thu, 2018-05-17 at 15:18 +0300, Serhiy Storchaka wrote: Does anyone has the full copy of the PyXML repository, with the complete history? This library was included in Python 2.1 as the xml package and is not maintained as a separate project since 2004. It's home on SourceForge was removed. I have found sources of the last PyXML version (0.8.4), but without history. Did you try asking SourceForge if they still have a backup copy? No, I didn't. I first tried to ask whether any of active Python core developers were involved in developing of PyXML and kept some history. I even don't know whether PyXML used any VCS served by SourceForge, or just published tarballs. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] When tp_clear returns non-zero?
The tp_clear field of PyTypeObject has type inquiry. It is a pointer to a function that takes PyObject * and return int. typedef int (*inquiry)(PyObject *); I'm interesting what the result of this function means. In what cases it can return non-zero, and can it set an exception? Currently tp_clear() is called in a single place, and its result is ignored. All tp_clear implementations in the stdlib always return 0. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
AFAIK there's no setting like this available, and I've done this many times on other repos with no trouble. Maybe it could be a GitHub bug? On May 28, 2018 4:59:03 AM Victor Stinner wrote: Hi, Since one or two weeks, I noticed that it's difficult to merge pull requests into the 2.7 branch. If a different commit is pushed in the meanwhile (if a different PR has been merged), the 2.7 branch diverges and the PR is immediately marked as "This branch is out-of-date with the base branch" and the "Squash and Merge" button is disabled (grey). For example my PR https://github.com/python/cpython/pull/7120 which changes Lib/test/regrtest.py cannot be merged because a commit touching the documentation (Doc/ directory) has been merged after I posted my PR and before the CI completed. I don't see the same behavior on the master branch. Is the 2.7 branch configured as more strict? Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
Ryan is right that there's no special setting in GitHub at least which would make merging more strict for certain branches as you're describing. On Mon, 28 May 2018 at 07:06 Ryan Gonzalez wrote: > AFAIK there's no setting like this available, and I've done this many > times > on other repos with no trouble. Maybe it could be a GitHub bug? > > > On May 28, 2018 4:59:03 AM Victor Stinner wrote: > > > Hi, > > > > Since one or two weeks, I noticed that it's difficult to merge pull > > requests into the 2.7 branch. If a different commit is pushed in the > > meanwhile (if a different PR has been merged), the 2.7 branch diverges > > and the PR is immediately marked as "This branch is out-of-date with > > the base branch" and the "Squash and Merge" button is disabled (grey). > > > > For example my PR https://github.com/python/cpython/pull/7120 which > > changes Lib/test/regrtest.py cannot be merged because a commit > > touching the documentation (Doc/ directory) has been merged after I > > posted my PR and before the CI completed. > > > > I don't see the same behavior on the master branch. Is the 2.7 branch > > configured as more strict? > > > > Victor > > ___ > > Python-Dev mailing list > > [email protected] > > https://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: > > https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com > > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] When tp_clear returns non-zero?
On 2018-05-28, Serhiy Storchaka wrote: > I'm interesting what the result of this function means. In what > cases it can return non-zero, and can it set an exception? My memory is fuzzy (nearly 20 years since I wrote that code). My best guess is that I thought a return value might be useful somehow. As you have noticed, the return type probably should have been void. If you want to see one of the first implementations of the Python GC, I still have a patch: http://python.ca/nas/python/gc/gc-cycle-152.diff Regards, Neil ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
Isn't that what happens if someone enables the check box at Repository Settings -> Branches -> Branch protection rules -> [pick a branch] -> Require branches to be up to date before merging ? On Mon, May 28, 2018, 09:11 Brett Cannon wrote: > Ryan is right that there's no special setting in GitHub at least which > would make merging more strict for certain branches as you're describing. > > On Mon, 28 May 2018 at 07:06 Ryan Gonzalez wrote: > >> AFAIK there's no setting like this available, and I've done this many >> times >> on other repos with no trouble. Maybe it could be a GitHub bug? >> >> >> On May 28, 2018 4:59:03 AM Victor Stinner wrote: >> >> > Hi, >> > >> > Since one or two weeks, I noticed that it's difficult to merge pull >> > requests into the 2.7 branch. If a different commit is pushed in the >> > meanwhile (if a different PR has been merged), the 2.7 branch diverges >> > and the PR is immediately marked as "This branch is out-of-date with >> > the base branch" and the "Squash and Merge" button is disabled (grey). >> > >> > For example my PR https://github.com/python/cpython/pull/7120 which >> > changes Lib/test/regrtest.py cannot be merged because a commit >> > touching the documentation (Doc/ directory) has been merged after I >> > posted my PR and before the CI completed. >> > >> > I don't see the same behavior on the master branch. Is the 2.7 branch >> > configured as more strict? >> > >> > Victor >> > ___ >> > Python-Dev mailing list >> > [email protected] >> > https://mail.python.org/mailman/listinfo/python-dev >> > Unsubscribe: >> > https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com >> >> >> ___ >> Python-Dev mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> https://mail.python.org/mailman/options/python-dev/brett%40python.org >> > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/njs%40pobox.com > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
On May 28, 2018, at 13:19, Nathaniel Smith wrote: > > Isn't that what happens if someone enables the check box at Repository > Settings -> Branches -> Branch protection rules -> [pick a branch] -> Require > branches to be up to date before merging ? Hmm, for some some reason, it appears that, at the moment, the 2.7, 3.4, and 3.5 branches have that option set, while 3.6, 3.7, and master don't. I'm not sure how we got to that state. Any other reasons to prefer on versus off? On Mon, May 28, 2018, 09:11 Brett Cannon wrote: > Ryan is right that there's no special setting in GitHub at least which would > make merging more strict for certain branches as you're describing. > > On Mon, 28 May 2018 at 07:06 Ryan Gonzalez wrote: > AFAIK there's no setting like this available, and I've done this many times > on other repos with no trouble. Maybe it could be a GitHub bug? > > On May 28, 2018 4:59:03 AM Victor Stinner wrote: > > > Hi, > > > > Since one or two weeks, I noticed that it's difficult to merge pull > > requests into the 2.7 branch. If a different commit is pushed in the > > meanwhile (if a different PR has been merged), the 2.7 branch diverges > > and the PR is immediately marked as "This branch is out-of-date with > > the base branch" and the "Squash and Merge" button is disabled (grey). > > > > For example my PR https://github.com/python/cpython/pull/7120 which > > changes Lib/test/regrtest.py cannot be merged because a commit > > touching the documentation (Doc/ directory) has been merged after I > > posted my PR and before the CI completed. > > > > I don't see the same behavior on the master branch. Is the 2.7 branch > > configured as more strict? -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
On Mon, May 28, 2018 at 03:09:46PM +0300, Serhiy Storchaka wrote: > 25.05.18 05:09, Jan Claeys пише: > > On Thu, 2018-05-17 at 15:18 +0300, Serhiy Storchaka wrote: > > > Does anyone has the full copy of the PyXML repository, with the > > > complete history? > > > > > > This library was included in Python 2.1 as the xml package and is > > > not maintained as a separate project since 2004. It's home on > > > SourceForge was removed. I have found sources of the last PyXML > > > version (0.8.4), but without history. > > > > > > > Did you try asking SourceForge if they still have a backup copy? > > No, I didn't. I first tried to ask whether any of active Python core > developers were involved in developing of PyXML and kept some history. I > even don't know whether PyXML used any VCS served by SourceForge, or just > published tarballs. They had been using CVS: https://web.archive.org/web/20151113082010/http://sourceforge.net/p/pyxml/code/ CVS repo web viewer shows some subdirectories but it seems there is no sources. I also failed to rsync from their CVS pserver and I doubt they have a backup -- SF stopped supporting CVS long ago. Oleg. -- Oleg Broytmanhttps://phdru.name/[email protected] Programmers don't die, they just GOSUB without RETURN. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
On Mon, May 28, 2018 at 2:11 PM, Jeremy Kloth wrote: > Here you go! > > https://github.com/jkloth/pyxml I did forget to mention that I was one of the prior maintainers on the PyXML project as well. -- Jeremy Kloth ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
On Thu, May 17, 2018 at 6:18 AM, Serhiy Storchaka wrote: > Does anyone has the full copy of the PyXML repository, with the complete > history? > > This library was included in Python 2.1 as the xml package and is not > maintained as a separate project since 2004. It's home on SourceForge was > removed. I have found sources of the last PyXML version (0.8.4), but without > history. > > I'm trying to figure out some intentions and fix possible bugs in the xml > package. The history of all commits could help. Here you go! https://github.com/jkloth/pyxml -- Jeremy Kloth ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
2018-05-28 19:47 GMT+02:00 Ned Deily : > Hmm, for some some reason, it appears that, at the moment, the 2.7, 3.4, and > 3.5 branches have that option set, while 3.6, 3.7, and master don't. I'm not > sure how we got to that state. Any other reasons to prefer on versus off? As I wrote, it became very difficult to merge any PR on 2.7 because of that. We all run a race to be the first one to merge a change into 2.7. The next one will get a "conflict" even if the merged commit is unrelated (as I described: two different unrelated directories). Please use the same configuration for 2.7, 3.6, 3.7 and master branches! Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
On May 28, 2018, at 17:42, Victor Stinner wrote: > 2018-05-28 19:47 GMT+02:00 Ned Deily : >> Hmm, for some some reason, it appears that, at the moment, the 2.7, 3.4, and >> 3.5 branches have that option set, while 3.6, 3.7, and master don't. I'm >> not sure how we got to that state. Any other reasons to prefer on versus >> off? > > As I wrote, it became very difficult to merge any PR on 2.7 because of > that. We all run a race to be the first one to merge a change into > 2.7. The next one will get a "conflict" even if the merged commit is > unrelated (as I described: two different unrelated directories). > > Please use the same configuration for 2.7, 3.6, 3.7 and master branches! Sounds reasonable. I've updated the 2.7 configuration to match the others and not require the PR branch be up to date before merging, meaning the CI test might be against an older view of the branch. If it proves to be a problem, we can revisit it for all of the branches. I am not going to change the settings for 3.5 and 3.4 as they are in security-fix mode and only their release manager can merge changes for those. -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
Wow. Thanks! On Mon, May 28, 2018 at 1:14 PM, Jeremy Kloth wrote: > On Mon, May 28, 2018 at 2:11 PM, Jeremy Kloth > wrote: > > Here you go! > > > > https://github.com/jkloth/pyxml > > I did forget to mention that I was one of the prior maintainers on the > PyXML project as well. > > -- > Jeremy Kloth > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
On Thursday, May 17, 2018, Serhiy Storchaka wrote: > [...] > > I'm trying to figure out some intentions and fix possible bugs in the xml > package. defusedxml https://pypi.org/project/defusedxml/ > XML bomb protection for Python stdlib modules https://pypi.org/project/defusedxml/#how-to-avoid-xml-vulnerabilities """ Best practices - Don’t allow DTDs - Don’t expand entities - Don’t resolve externals - Limit parse depth - Limit total input size - Limit parse time - Favor a SAX or iterparse-like parser for potential large data - Validate and properly quote arguments to XSL transformations and XPath queries - Don’t use XPath expression from untrusted sources - Don’t apply XSL transformations that come untrusted sources """ https://github.com/tiran/defusedxml > The history of all commits could help. > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/wes. > turner%40gmail.com > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] The history of PyXML
28.05.18 23:11, Jeremy Kloth пише: On Thu, May 17, 2018 at 6:18 AM, Serhiy Storchaka wrote: Does anyone has the full copy of the PyXML repository, with the complete history? This library was included in Python 2.1 as the xml package and is not maintained as a separate project since 2004. It's home on SourceForge was removed. I have found sources of the last PyXML version (0.8.4), but without history. I'm trying to figure out some intentions and fix possible bugs in the xml package. The history of all commits could help. Here you go! https://github.com/jkloth/pyxml Great! Thank you, this is what I needed! ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
