This script requires two Python dependencies: beautifulsoup4
and openpyxl
. Install them first using pip:
$ pip install beautifulsoup4
$ pip install openpyxl
You might have to use sudo
if installing globally.
import asyncio | |
import random | |
from time import time, sleep as _sleep | |
""" | |
This gist helps understand the basic implementation of the parallel and series call in python using the asyncio library. | |
The code demonstrates how to invoke asyncio functions and non-asyncio functions asynchronously. | |
Note from the below output - the parallel calls will always be completed in the ascending order of the sleep seconds, | |
where as the series call will be completed in the ascending order of the call id. |
This script requires two Python dependencies: beautifulsoup4
and openpyxl
. Install them first using pip:
$ pip install beautifulsoup4
$ pip install openpyxl
You might have to use sudo
if installing globally.
This procedure explains how to install MySQL using Homebrew on macOS Sierra 10.12
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
At this time of writing, Homebrew has MySQL version 5.7.15 as default formulae in its main repository :
If you're doing stuff with Ruby on a Mac, e.g. installling Jekyll or something, by default you'll end up having to use the sudo
command to do stuff, since the permission to modify the default config is not available to your user account.
This sucks and should be avoided. Here's how to fix that.
To make this better, we are going install a new, custom Ruby. This used to be a big, scary thing, but thanks to the awesome tools Homebrew and rbenv, it's a snap.*
A word of warning: you will have to use Terminal to install this stuff. If you are uncomfortable with text, words, and doing stuff with your computer beyond pointing and hoping, this may not work well for you. But if that's the case, I'm not sure why you were trying to use Ruby in the first place.
I’m a web app that wants to allow other web apps access to my users’ information, but I want to ensure that the user says it’s ok.
I can’t trust the other web apps, so I must interact with my users directly. I’ll let them know that the other app is trying to get their info, and ask whether they want to grant that permission. Oauth defines a way to initiate that permission verification from the other app’s site so that the user experience is smooth. If the user grants permission, I issue an AuthToken to the other app which it can use to make requests for that user's info.
Oauth2 has nothing to do with encryption -- it relies upon SSL to keep things (like the client app’s shared_secret) secure.
Let’s say your GitHub username is “alice”. If you create a GitHub repository named alice.github.com, commit a file named index.html into the master branch, and push it to GitHub, then this file will be automatically published to http://alice.github.com/... The same works for organizations.
Read more here: http://pages.github.com/
However... the downside of this is that anyone that forks this repo won't get it as a GitHub Pages repo when they are working on it... because they have a different GitHub "username" (or "organisation name").
So the trick is to not use a master
branch as the documentation tells you... rather, use a gh-pages
branch, as you would for your other "Project Pages".