recentpopularlog in

kme : path   20

windows - Run Python scripts in PowerShell directly - Super User
Edit the PATHEXT environment variable and add the .py extension.

Just add this line to your powershell profile:
<code class="language-powershell">$env:PATHEXT += ";.py"</code>

or you could just edit PATHEXT globally using the system settings (just start menu search for "Edit Environment variables for your account").


See https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles; the MS TechNet article linked in the approved answer is looooong dead.
python  powershell  windows  cli  commandline  pathext  path  environmentvariable  shellscripting  solution  essential  movein  configuration 
6 weeks ago by kme
pip install --user should check that the user's $PATH is correct · Issue #3813 · pypa/pip | https://github.com/
On Unix, pip install --user ... drops scripts into ~/.local/bin. Historically, this directory has not been on the default Debian/Ubuntu $PATH. This is hopefully on its way to being fixed (bash 4.3-15 is on its way into Debian unstable no...
pip  path  configfile  bashrc  bash_profile  solution  newbie 
march 2019 by kme
git aliases causing "Permission denied" error - Stack Overflow
The correct answer to this was actually different. Before git runs the aliases it checks the $PATH. In case the directory does not exist, or lacks permissions, git produces the "fatal: cannot exec 'git-co': Permission denied". It does not ever comes to check the aliases so git foobar will produce the same error.

Good people from the git mailing list also reminded me of an strace tool, that can help finding the entry that is returning EACCES, as in: strace -f -e execve git foobar

The credit goes to Jeff King from the git mailing list. :)
git  git-alias  bizarre  path  environmentvariable  strace  linux  troubleshooting  solution 
june 2015 by kme
path - Which setup files should be used for setting up environment variables with bash? - Super User
Note that sometimes you'll see recommendations to either set environment variables in ~/.bashrc, or start a login shell in each terminal in a GUI environment. Both are bad ideas; one of the reasons is the problem you've experienced, namely that your environment variables were only available in programs started via a terminal, and not in programs started directly with an icon or menu or keyboard shortcut.
bash  shell  dotfiles  rcfiles  initfile  path  environmentvariables  wrongforsolong  solution 
may 2015 by kme
bash - Duplicate entries in $PATH a problem? - Unix & Linux Stack Exchange
Side note: .bashrc is not the right place to set $PATH or any other environment variable. Environment variables should be set in ~/.profile. See Which setup files should be used for setting up environment variables with bash?, Difference between .bashrc and .bash_profile.
bash  path  rcfiles  dotfiles  sysadmin  ohsothatswhy  wrongforsolong  solution 
may 2015 by kme
Practical mod_perl: 3.9.2.1. Modifying @INC
use lib qw(/home/stas/lib/perl5/5.6.1/
/home/stas/lib/perl5/site_perl/5.6.1
/home/stas/lib/perl5/site_perl
);

Another way is to write code to modify @INC explicitly:

BEGIN {
unshift @INC,
qw(/home/stas/lib/perl5/5.6.1/i386-linux
/home/stas/lib/perl5/5.6.1
/home/stas/lib/perl5/site_perl/5.6.1/i386-linux
/home/stas/lib/perl5/site_perl/5.6.1
/home/stas/lib/perl5/site_perl
);
}
perl  modules  path  devel  webdevel  solution 
october 2014 by kme

Copy this bookmark:





to read