Pipenv – Python Package Manager and Virtual environment manager
Venv – Virtual environment manager
Virtualenv – Virtual environment manager
Installing Python Runtime Versions via Pyenv
In order to test different Python Runtime versions, I have installed some versions.
$ pyenv install 3.10.2
python-build: use openssl@1.1 from homebrew
python-build: use readline from homebrew
Downloading Python-3.10.2.tar.xz...
-> https://www.python.org/ftp/python/3.10.2/Python-3.10.2.tar.xz
Installing Python-3.10.2...
python-build: use tcl-tk from homebrew
python-build: use readline from homebrew
python-build: use zlib from xcode sdk
Installed Python-3.10.2 to /Users/kenanhancer/.pyenv/versions/3.10.2
I have 4 Python runtime versions(3.10.2, 3.10.3, 3.10.4, 3.10.5) in my machine.
$ pyenv versions
system
3.10.2
3.10.3
3.10.4
* 3.10.5 (set by /Users/kenanhancer/.pyenv/version)
When we want to check whether current terminal is attached to stdin, stdout and stderr streams or not, we can use the below codes. I tried with piping, and redirection so both works well.
As seen in below 6 usages, stdin is not listed in output of commands except first one. Because stdin is used by piping or redirection.
$ . ./getProcess.sh
Organization: kenanhancer
Process Name: Agile
PAT: blablabla
{
"id": "adcc42ab-9882-485e-a3ed-7678f01f66bc",
"description": "This template is flexible and will work great for most teams using Agile planning methods, including those practicing Scrum.",
"isDefault": true,
"_links": {
"self": {
"href": "https://dev.azure.com/kenanhancer/_apis/process/processes/adcc42ab-9882-485e-a3ed-7678f01f66bc"
}
},
"type": "system",
"url": "https://dev.azure.com/kenanhancer/_apis/process/processes/adcc42ab-9882-485e-a3ed-7678f01f66bc",
"name": "Agile"
}
Sign in to your organisation (https://dev.azure.com/{yourorganization})
Treat and use a PAT like your password and keep it a secret.
Use your PAT anywhere your user credentials are required for authentication in Azure DevOps.
You can use a personal access token (PAT) as an alternate password to authenticate into Azure DevOps.
A personal access token contains your security credentials for Azure DevOps. A PAT identifies you, your accessible organizations, and scopes of access. As such, they're as critical as passwords, so you should treat them the same way.
If you're working within Microsoft tools, then your Microsoft account (MSA) or Azure Active Directory (Azure AD) is an acceptable and well-supported approach. But, if you're working with third-party tools that don't support Microsoft or Azure AD accounts – or you don't want to provide your primary credentials to the tool – use PATs to limit your risk.
find more details about creating PAT in Azure DevOps
I will not write all story here but people were using Teletypewriter(TTY) from 1830s and 1840s. As seen in the following pictures, it was a semi-electronic device, there wasn't any monitor, output was written in a paper.
Novadays, we use computers with monitor and operating system but Linux still uses TTY concept under the hood 🙂
You can find some diagrams below relation with Terminal Emulator and TTY
Teletypewriter(Teletype, Teleprinter or TTY)A restored 1930s Teletype is now a Linux TTYA Teletype Model 32 ASR used for Telex serviceVideo terminals like the DEC VT-100 (1978) made teletypes obsolete as computer I/O devicesTerminal Emulator (Pseudo type writer or PTY)Each Terminal Emulator window attached to separate TTY as shown in the above screenshot.Continue reading →