Just leaving this here for my own sake, after having to deal with these annoying issues on the macOS Mojave Beta. When trying to build various Homebrew apps that use Python (or are Python) I ran into something like this:
Traceback (most recent call last):
File "/usr/local/bin/pip3", line 11, in
load_entry_point('pip==10.0.1', 'console_scripts', 'pip3')()
File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 476, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2700, in load_entry_point
File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2318, in load
File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2324, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/__init__.py", line 20, in
from pip._vendor.urllib3.exceptions import DependencyWarning
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/__init__.py", line 8, in
from .connectionpool import (
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/connectionpool.py", line 36, in
from .response import HTTPResponse
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 3, in
ModuleNotFoundError: No module named 'zlib'
The fix is as follows, thanks to sfdye over at GitHub:
$ brew update
# (Re)Install CLT (command in one line):
$ sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target /
Then reinstall your Homebrew Python version with something like
$ brew reinstall python@2
That stopped these zlib errors for me.
Using macOS High Sierra? Make sure to give your root user a password, because of this serious security issue:
Update: Check the Mac App Store for Apple’s official fix. It’s being automatically pushed to your Mac as well.
Dave Mark writing for The Loop:
I love this tip. Here’s how to do it:
– Bring up Apple Maps.
– Double-tap in the map, but on the second tap, don’t lift your finger. So tap-lift-tap-leave.
– Now [with the finger still down] slide up or down to zoom in and out.
As Dave notes Google Maps supports the same gesture. It actually has supported this for ages and I always found myself trying to do this in Apple Maps. With iOS 11 I was happy to find out it finally works the same. Well, I should rather say works similar, because the directions are flipped on Google Maps: move your finger up to zoom out and down to zoom in.
Photoshop Lightroom on your iPhone and iPad does not support the native use of user defined (Smart) Filters. And unlike photos you aren’t able sync to them to your devices either. However there’s a trick to be able to use filters you have in Lightroom on your desktop on your smartphone and tablet. Continue reading “Adobe Lightroom: How to use user defined filters on your iPhone and iPad”
Facebook buying Instagram
When Mike and I started Instagram nearly two years ago, we set out to change and improve the way the world communicates and shares. Weâ€™ve had an amazing time watching Instagram grow into a vibrant community of people from all around the globe. Today, we couldnâ€™t be happier to announce that Instagram has agreed to be acquired by Facebook.
Now that Facebook has acquired Instagram, I’m sure some people are trying to figure out how to get their photos out of it. Instaport.me is one service that offers you a way to export your pictures from Instagram.
After authenticating with your Instagram credentials, Instaport will gather your photos and offer you a ZIP file after it’s done. I had 232 photos which were 21.3 MB. Here’s the link to delete your Instagram account in case you were looking.
Congrats on that $1 billion though!
This is more of a “note to self”: After enabling FileVault on my MBP during installation, the input field for entering your FileVault password is using the US keyboard layout. That, in combination with an actual German keyboard, is good for some fun during your next reboot â€“ of course only if you’re using a strong password, which includes special characters.
To be able to change the keyboard layout at boot, you have to tick the box as seen above.
Those of you who are using the updated versions of Xcode, like Xcode 4.3 or 4.4 â€“ which is available for the Mountain Lion Developer Preview â€“ will probably run into an issue with homebrew at some point.
Xcode doesn’t install into /Developer any longer and is now an app bundle like most other Mac apps. Homebrew though expects some files to be available on your Mac to do its job, cc just being one of them. As a result, running brew doctor will tell you that something is wrong with your setup.
To get these command line tools back, you have to install them manually (via Homebrew on Github). After installing Xcode you get them by doing the following (see screenshot above):
- Open Xcode
- Go to Preferences
- Select Downloads and click Install for Command Line Tools (about 171 Megabyte)
There you go, brew doctor will be happy with you again.
For Lion there’s now also just a Command Line Tools download. It requires a free Apple ID to access them. Be sure to check Kenneth Reitz’ blog post about it.
Haven’t tried it yet, but the process for creating a bootable OS X Mountain Lion install medium (USB stick or DVD) should be the same as it was for OS X 10.7. Same filenames, same places, slightly new icons, definitely new content.
The whole Dropbox idea has been a very successful story so far. And now they’re apparently looking to get photographers to use their service. A recently released experimental version â€“ read “you should backup your files or otherwise it might eat them along with your firstborn” â€“ now comes with an integrated tool that detects a camera or memory card once you plug it into your USB port. There’s also an experimental Android version available (APK here) that uploads files automatically in the background using 3G or Wi-Fi.
After detecting a camera/card you are presented with a simple screen (see above), asking whether or not you’d like to import the photos and videos to your Dropbox. All uploaded files then show up in a new “Camera Uploads” folder and will be saved in the cloud.
Dropbox Photo Import also comes with a little gem: For the first upload you get 500 MByte, afterwards for every 500 MByte uploaded you’ll also receive 500 MByte of space. In total you can reach up to 5 GByte this way.
It worked flawlessly with some Nikon RAW files (NEF) I threw at it, although CPU usage was rather high for what looks like a simple copy process. On Windows you have to have AutoPlay enabled to make it work. Linux or Mac OS X 10.4 aren’t supported. Here are some screenshots using the app on OS X 10.7.3:
The forum post also has some other hints:
- For Android devices, it’s best to use “Connect as Disk Drive”. HTC Sync will not work.
To import from iPhone, make sure to unlock your phone and enter your passcode before importing, otherwise it will claim to find no photos.
- If importing from your iPhone on Mac gives an import error, try hard resetting it–hold down the power and the home button for 5 seconds. This will reboot the phone; it shouldn’t change your settings or delete data.
- On Windows, this feature relies on Autoplay. Please enable Autoplay to use this feature if you have disabled it.
- On XP and Vista, it relies on the Windows Image Acquisition Service. If this service is not started, please start the service and reinstall Dropbox to use this feature. On WIndows Server, you may have to install the Desktop Experience feature.
- On Windows 7, newer devices that rely on Device Stage (in the Control Panel) will not show Dropbox as an import option until you select “Change Program” for the default.
- The Galaxy Nexus takes a lot of time to connect on OS X because it likes to pretend that every image on the device is a photograph. We now estimate how long it’s going to take and show you that in the progress bar but it’s usually in the order of minutes. We’re working to see if this can be improved.
Well, here’s one iOS 5 issue that came up recently on Apple’s discussion forums: You switch from an iPhone with iMessage enabled to another smartphone that doesn’t have any idea on what iMessage is, for example an Android or Windows smartphone. Your friends using an iPhone will continue sending iMessages to your non-existent iPhone, because your phone number is still associated with your old iOS device.
A similar issue might show up if you sell or lose your iPhone. The new owner might continue to get your iMessages.
There’s a possible solution to this, as mentioned on the forums:
- Go to: https://supportprofile.apple.com/MySupportProfile.do
- Log in if not already logged in.
- Click on “edit products”
- Click on the “x” to the right of the product.
- Click “unregister”
In case the click on ‘x’ doesn’t show the “unregister” button, you can just select the device you want to get rid of and remove it from within details page of said device.
Hope this helps in case you’re having issues with a lost or sold iPhone that’s still getting your iMessages.