From ronaldoussoren at mac.com Sun Apr 1 07:52:11 2018 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Sun, 01 Apr 2018 13:52:11 +0200 Subject: [Pythonmac-SIG] ANN: PyObjC 4.2 Message-ID: I?ve just published PyObjC 4.2 on PyPI. This is primarily a bug fix release, but also introduces bindings to the BusinessChat framework introduced in macOS 10.13.4. Those bindings are probably totally uninteresting for most users as the framework can only be used by a small subset of macOS developers. The full list of changes for this release: * Add bindings to the BusinessChat framework introduced in macOS 10.13.4 * Update metadata for Xcode 9.3 * Issue #233 Fix crash in Security.AuthorizationCopyRights() wrapper * Issue #234 Fix crash in AuthorizationExecuteWithPrivileges() wrapper Reported by Vangelis Koukis * Ensure doctest can work with modules containing subclasses of NSObject Reported by Just van Rossum * Issue #236 : Importing can sometimes fail in multi-threaded scenarios Fix by Max B?langer * Undeprecate treating struct wrappers as sequences. Removing this feature would break too much existing code, hence deprecating is not really an option. Furthermore, this would also break some nice idioms. * Pull request #17: Fix python 3 issues in PyObjCTools.AppHelper and PyObjCTools.Conversion Fix by Max B?langer Regards, Ronald -------------- next part -------------- An HTML attachment was scrubbed... URL: From ronaldoussoren at mac.com Mon Apr 2 04:10:56 2018 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Mon, 02 Apr 2018 10:10:56 +0200 Subject: [Pythonmac-SIG] Argument is a block, but no signature available In-Reply-To: <1E4A90C1-B222-4991-A0AF-1444718E059F@me.com> References: <1E4A90C1-B222-4991-A0AF-1444718E059F@me.com> Message-ID: > On 16 Mar 2018, at 20:39, Ben Byram-Wigfield wrote: > > I?m trying to use a Completion Handler block as an argument for a Cocoa AVMIDIPlayer method: > > midiPlayer = AVMIDIPlayer.alloc().initWithContentsOfURL_soundBankURL_error_(midiFile, None, None) > midiPlayer.prepareToPlay() > midiPlayer.play_(myCompletionHandler) > > But I get: > > Argument 2 is a block, but no signature available > > From what I can find out, this points to a bit in the metadata of PyObjC that needs a bit of work. Is that the case? That?s correct. > > I?m using the default version 2.5.1 bundled with MacOS. That?s your problem, 2.5 is ancient and unmaintained. I?ve checked the metadata for PyObjC 4.2 (released yesterday) and that has metadata for this API. Ronald From sh at changeset.nyc Mon Apr 2 16:36:29 2018 From: sh at changeset.nyc (Sumana Harihareswara) Date: Mon, 2 Apr 2018 16:36:29 -0400 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) Message-ID: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Mac users: If you are running macOS/OS X version 10.12 or older, you need to upgrade to the latest pip (9.0.3) to connect to the Python Package Index securely: curl https://bootstrap.pypa.io/get-pip.py | python Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ Context: As PSF blogged last year https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html , on June 30, 2018, Python.org sites are going to entirely stop supporting TLS versions 1.0 and 1.1, because our CDN provider is deprecating support for those versions. We are launching the new PyPI (in beta at https://pypi.org) this month and replacing the legacy PyPI (https://pypi.python.org). Here's the beta announcement for the new PyPI: https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html Warehouse, the codebase for the new PyPI, does not support TLS 1.0 or 1.1. We're warning our users early with this message. Also, as of late March, the Python Package Index has started doing brownouts of the deprecated TLS versions. For some portion of each hour, anyone attempting to access PyPI with TLSv1.0 or TLSv1.1 will get a 403 response with an informative error. As we get closer to the deadline, we will be ramping up the amount of time the endpoint is down for the deprecated TLS versions. The ultimate goal is to have it be 100% unavailable on and after April 8th, prior to the final deadline (because we can give a good error message -- once June 30th hits, it will just be an uninformative OpenSSL error). More info: * https://github.com/pypa/warehouse/issues/3293 * https://github.com/pypa/warehouse/issues/3411 * https://status.python.org/incidents/btjtz01lzp88 Thank you. Please publicize this. -- Sumana Harihareswara Warehouse project manager Changeset Consulting https://changeset.nyc From ronaldoussoren at mac.com Tue Apr 3 15:58:39 2018 From: ronaldoussoren at mac.com (Ronald Oussoren) Date: Tue, 03 Apr 2018 21:58:39 +0200 Subject: [Pythonmac-SIG] ANN: PyObjC 4.2.1 Message-ID: Hi, I just pushed PyObjC 4.2.1 to PyPI. This is a very minor bug fix release and most people don?t have to upgrade. There?s only a single fix for some people from source: the automatic detection of the use of ??with-system-ffi? works again (it was disabled in 4.2 because that feature didn?t work with /usr/bin/python). The fix doesn?t affect users of binary wheels. Ronald From matthew.brett at gmail.com Fri Apr 6 09:24:21 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Fri, 6 Apr 2018 14:24:21 +0100 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Message-ID: Hi, On Mon, Apr 2, 2018 at 9:36 PM, Sumana Harihareswara wrote: > Mac users: > > If you are running macOS/OS X version 10.12 or older, you need to > upgrade to the latest pip (9.0.3) to connect to the Python Package Index > securely: > > curl https://bootstrap.pypa.io/get-pip.py | python > > Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < > 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ I wanted to check with you, whether these changes are responsible for pip breaking for me in a extremely confusing way. What I observed was that pip was silently failing to find any packages on pypi, with no informative error. This was extremely confusing, because when I tried to do an upgrade, e.g.: $ pip install -U matplotlib it told me everything is up to date, when this isn't correct. There is no other message to warn me what is going on. Of course I can't upgrade pip in the usual way, and I get told I am up to date, when I am not. $ python -m pip install -U pip Requirement already up-to-date: pip in /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages I assume there was meant to be some more informative message about what is happening? Even with such a message this is going to cause a significant problem, but without it, it's going to cause total chaos. Cheers, Matthew From matthew.brett at gmail.com Fri Apr 6 10:47:09 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Fri, 6 Apr 2018 15:47:09 +0100 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: <1523021524.698165.1328833408.67C8DCA8@webmail.messagingengine.com> References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> <1523021524.698165.1328833408.67C8DCA8@webmail.messagingengine.com> Message-ID: Hi, On Fri, Apr 6, 2018 at 2:32 PM, Sumana Harihareswara wrote: > Sorry to be terse - I am attending to some family stuff for the next few days. > > Thanks for the report. You may be right - what happens when you use the -v option(s) to make the error message(s) show up? I think -vvv might do the trick. Yes, the message does appear with -v > The folks in #pypa on Freenode IRC and in https://github.com/pypa/packaging-problems/issues/134 (I think) may be able to provide more advice and get a bigger announcement going. I doubt very much that any announcement is going to get the attention of more than a small proportion of the people affected by this. The problem is that, using pip's current defaults, pip goes from working correctly, to silently broken. I'll try seeing if I can subvert issue 134 for a discussion. Cheers, Matthew From sh at changeset.nyc Fri Apr 6 09:32:04 2018 From: sh at changeset.nyc (Sumana Harihareswara) Date: Fri, 06 Apr 2018 09:32:04 -0400 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Message-ID: <1523021524.698165.1328833408.67C8DCA8@webmail.messagingengine.com> Sorry to be terse - I am attending to some family stuff for the next few days. Thanks for the report. You may be right - what happens when you use the -v option(s) to make the error message(s) show up? I think -vvv might do the trick. The folks in #pypa on Freenode IRC and in https://github.com/pypa/packaging-problems/issues/134 (I think) may be able to provide more advice and get a bigger announcement going. -- Sumana Harihareswara Changeset Consulting sh at changeset.nyc On Fri, Apr 6, 2018, at 9:24 AM, Matthew Brett wrote: > Hi, > > On Mon, Apr 2, 2018 at 9:36 PM, Sumana Harihareswara wrote: > > Mac users: > > > > If you are running macOS/OS X version 10.12 or older, you need to > > upgrade to the latest pip (9.0.3) to connect to the Python Package Index > > securely: > > > > curl https://bootstrap.pypa.io/get-pip.py | python > > > > Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < > > 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ > > I wanted to check with you, whether these changes are responsible for > pip breaking for me in a extremely confusing way. > > What I observed was that pip was silently failing to find any packages > on pypi, with no informative error. > > This was extremely confusing, because when I tried to do an upgrade, e.g.: > > $ pip install -U matplotlib > > it told me everything is up to date, when this isn't correct. There > is no other message to warn me what is going on. > > Of course I can't upgrade pip in the usual way, and I get told I am up > to date, when I am not. > > $ python -m pip install -U pip > Requirement already up-to-date: pip in > /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages > > I assume there was meant to be some more informative message about > what is happening? Even with such a message this is going to cause a > significant problem, but without it, it's going to cause total chaos. > > Cheers, > > Matthew From matthew.brett at gmail.com Fri Apr 6 13:45:35 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Fri, 6 Apr 2018 18:45:35 +0100 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Message-ID: Hi, On Fri, Apr 6, 2018 at 6:06 PM, Chris Jerdonek wrote: > > On Fri, Apr 6, 2018 at 6:25 AM Matthew Brett > wrote: >> >> Hi, >> >> On Mon, Apr 2, 2018 at 9:36 PM, Sumana Harihareswara >> wrote: >> > Mac users: >> > >> > If you are running macOS/OS X version 10.12 or older, you need to >> > upgrade to the latest pip (9.0.3) to connect to the Python Package Index >> > securely: >> > >> > curl https://bootstrap.pypa.io/get-pip.py | python >> > >> > Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < >> > 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ >> >> I wanted to check with you, whether these changes are responsible for >> pip breaking for me in a extremely confusing way. >> >> What I observed was that pip was silently failing to find any packages >> on pypi, with no informative error. >> >> This was extremely confusing, because when I tried to do an upgrade, e.g.: >> >> $ pip install -U matplotlib >> >> it told me everything is up to date, when this isn't correct. There >> is no other message to warn me what is going on. > > > Can you paste the input / output that you saw or are seeing ? what you are > calling ?breaking for me in a extremely confusing way?? On the GitHub issue > thread in which this was discussed, the understanding is that people *would* > see errors that would lead them in the right direction (e.g. SSL errors). > What you?re saying seems to conflict with that. During the current brownout period, with the default use of pip, you get no error at all when you attempt to upgrade a package - it just says you're up to date - this (below) is the full output: $ python -m pip install -U pip Requirement already up-to-date: pip in /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages You are using pip version 9.0.1, however version 9.0.3 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Of course, it's very easy to miss that you don't have the latest version of the package in this case - everything looks like it worked correctly. If you try and install a package, it just says it can't find it, but not why: $ pip3.5 install transforms3d Collecting transforms3d Could not find a version that satisfies the requirement transforms3d (from versions: ) No matching distribution found for transforms3d You are using pip version 9.0.1, however version 9.0.3 is available. You should consider upgrading via the 'pip install --upgrade pip' command. You do get an informative message if you use the -v flag, but I rarely do that myself, and it's not the default. Just to give you an index of the problem, I got pretty confused myself when I asked pip to upgrade a package, it said it was already up to date, and I found I didn't have what I knew to be the right version, and I'm a very experienced pip user, who is also on various mailing lists where this was flagged. Cheers, Matthew From sh at changeset.nyc Fri Apr 6 14:02:38 2018 From: sh at changeset.nyc (Sumana Harihareswara) Date: Fri, 06 Apr 2018 14:02:38 -0400 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Message-ID: <1523037758.1685659.1329135608.656846A9@webmail.messagingengine.com> Matthew, Thank you for your detailed explanations and thoughts here and in https://groups.google.com/forum/m/#!topic/pypa-dev/Oz6SGA7gefo . I am not a Mac user and am fairly new to the Python packaging/distribution world, so this may be naive and unrealistic verging on ridiculous, but: is there anything we could ask Apple to do to help with this situation? Our upstream CDN (Fastly) is extremely unlikely to change their June 30th TLS 1.0/1.1 removal date, which would (I imagine) affect a ton of people on older Mac OS versions who do not even use PyPI. -- Sumana Harihareswara Changeset Consulting sh at changeset.nyc On Fri, Apr 6, 2018, at 1:45 PM, Matthew Brett wrote: > Hi, > > On Fri, Apr 6, 2018 at 6:06 PM, Chris Jerdonek wrote: > > > > On Fri, Apr 6, 2018 at 6:25 AM Matthew Brett > > wrote: > >> > >> Hi, > >> > >> On Mon, Apr 2, 2018 at 9:36 PM, Sumana Harihareswara > >> wrote: > >> > Mac users: > >> > > >> > If you are running macOS/OS X version 10.12 or older, you need to > >> > upgrade to the latest pip (9.0.3) to connect to the Python Package Index > >> > securely: > >> > > >> > curl https://bootstrap.pypa.io/get-pip.py | python > >> > > >> > Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < > >> > 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ > >> > >> I wanted to check with you, whether these changes are responsible for > >> pip breaking for me in a extremely confusing way. > >> > >> What I observed was that pip was silently failing to find any packages > >> on pypi, with no informative error. > >> > >> This was extremely confusing, because when I tried to do an upgrade, e.g.: > >> > >> $ pip install -U matplotlib > >> > >> it told me everything is up to date, when this isn't correct. There > >> is no other message to warn me what is going on. > > > > > > Can you paste the input / output that you saw or are seeing ? what you are > > calling ?breaking for me in a extremely confusing way?? On the GitHub issue > > thread in which this was discussed, the understanding is that people *would* > > see errors that would lead them in the right direction (e.g. SSL errors). > > What you?re saying seems to conflict with that. > > During the current brownout period, with the default use of pip, you > get no error at all when you attempt to upgrade a package - it just > says you're up to date - this (below) is the full output: > > $ python -m pip install -U pip > Requirement already up-to-date: pip in > /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages > You are using pip version 9.0.1, however version 9.0.3 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. > > Of course, it's very easy to miss that you don't have the latest > version of the package in this case - everything looks like it worked > correctly. > > If you try and install a package, it just says it can't find it, but not why: > > $ pip3.5 install transforms3d > Collecting transforms3d > Could not find a version that satisfies the requirement transforms3d > (from versions: ) > No matching distribution found for transforms3d > You are using pip version 9.0.1, however version 9.0.3 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. > > You do get an informative message if you use the -v flag, but I rarely > do that myself, and it's not the default. > > Just to give you an index of the problem, I got pretty confused myself > when I asked pip to upgrade a package, it said it was already up to > date, and I found I didn't have what I knew to be the right version, > and I'm a very experienced pip user, who is also on various mailing > lists where this was flagged. > > Cheers, > > Matthew From nad at python.org Fri Apr 6 15:11:02 2018 From: nad at python.org (Ned Deily) Date: Fri, 6 Apr 2018 15:11:02 -0400 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: <1523037758.1685659.1329135608.656846A9@webmail.messagingengine.com> References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> <1523037758.1685659.1329135608.656846A9@webmail.messagingengine.com> Message-ID: On Apr 6, 2018, at 14:02, Sumana Harihareswara wrote: > I am not a Mac user and am fairly new to the Python packaging/distribution world, so this may be naive and unrealistic verging on ridiculous, but: is there anything we could ask Apple to do to help with this situation? For the most part, the current problematic software is not shipped by Apple, other than the deprecated OpenSSL libraries, so I don't think there is realistically anything they could do to help. Here is my understanding of the situation regarding Pythons provided by python.org installers: https://github.com/pypa/warehouse/issues/3293#issuecomment-378468534 -- Ned Deily nad at python.org -- [] From matthew.brett at gmail.com Fri Apr 6 19:13:47 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Sat, 7 Apr 2018 00:13:47 +0100 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: <1523037758.1685659.1329135608.656846A9@webmail.messagingengine.com> References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> <1523037758.1685659.1329135608.656846A9@webmail.messagingengine.com> Message-ID: Hi, On Fri, Apr 6, 2018 at 7:02 PM, Sumana Harihareswara wrote: > Matthew, > > Thank you for your detailed explanations and thoughts here and in > https://groups.google.com/forum/m/#!topic/pypa-dev/Oz6SGA7gefo . > > I am not a Mac user and am fairly new to the Python packaging/distribution world, so this may be naive and unrealistic verging on ridiculous, but: is there anything we could ask Apple to do to help with this situation? > > Our upstream CDN (Fastly) is extremely unlikely to change their June 30th TLS 1.0/1.1 removal date, which would (I imagine) affect a ton of people on older Mac OS versions who do not even use PyPI. Sorry, I'm afraid I set off the discussion in the pypa thread you pointed to above. Reporting back here, for those not on the pypa-dev Google group - it looks like the TLS 1.0 shutdown is being driven by the Warehouse release, which I believe is planned for the 16th of April (Warehouse can't use TLS 1.0). In practice, there is no way of giving the users a better or more visible warning message than the message we are currently getting from using the -v flag. I'm arguing over in that thread, that it would be better to give up on the -v flag warning, and go straight to an SSL error (which has an uninformative message - see [1]), because the current situation, where pip silently fails to upgrade, including failing to upgrade itself, is more confusing than the SSL error. Do people agree / disagree? Cheers, Matthew [1] https://github.com/pypa/warehouse/issues/3293#issuecomment-378480462 From chris.jerdonek at gmail.com Fri Apr 6 13:06:36 2018 From: chris.jerdonek at gmail.com (Chris Jerdonek) Date: Fri, 06 Apr 2018 17:06:36 +0000 Subject: [Pythonmac-SIG] Upgrade to pip 9.0.3 (due to TLS deprecation) In-Reply-To: References: <5505f566-bc6c-9ead-e2b1-4651d03d4a95@changeset.nyc> Message-ID: On Fri, Apr 6, 2018 at 6:25 AM Matthew Brett wrote: > Hi, > > On Mon, Apr 2, 2018 at 9:36 PM, Sumana Harihareswara > wrote: > > Mac users: > > > > If you are running macOS/OS X version 10.12 or older, you need to > > upgrade to the latest pip (9.0.3) to connect to the Python Package Index > > securely: > > > > curl https://bootstrap.pypa.io/get-pip.py | python > > > > Pip 9.0.3 supports TLSv1.2 when running under system Python on macOS < > > 10.13. Official release notes: https://pip.pypa.io/en/stable/news/ > > I wanted to check with you, whether these changes are responsible for > pip breaking for me in a extremely confusing way. > > What I observed was that pip was silently failing to find any packages > on pypi, with no informative error. > > This was extremely confusing, because when I tried to do an upgrade, e.g.: > > $ pip install -U matplotlib > > it told me everything is up to date, when this isn't correct. There > is no other message to warn me what is going on. Can you paste the input / output that you saw or are seeing ? what you are calling ?breaking for me in a extremely confusing way?? On the GitHub issue thread in which this was discussed, the understanding is that people *would* see errors that would lead them in the right direction (e.g. SSL errors). What you?re saying seems to conflict with that. ?Chris > > Of course I can't upgrade pip in the usual way, and I get told I am up > to date, when I am not. > > $ python -m pip install -U pip > Requirement already up-to-date: pip in > > /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages > > I assume there was meant to be some more informative message about > what is happening? Even with such a message this is going to cause a > significant problem, but without it, it's going to cause total chaos. > > Cheers, > > Matthew > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG at python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG > -------------- next part -------------- An HTML attachment was scrubbed... URL: