3 ms·

I wrote a quick perl script earlier today to push crt.sh results for a bunch of domains into slack. Took about 30 minutes, far less time than messing about wit

I wrote a quick perl script earlier today to push crt.sh results for a bunch of domains into slack. Took about 30 minutes, far less time than messing about with why pip has broken on my desktop yet again: Traceback (most recent call last): File "/usr/local/bin/pip", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/pip/_internal/cli/main.py", line 73, in main command = create_command(cmd_name, isolated=("--isolated" in cmd_args)) File "/usr/local/lib/python3.5/dist-packages/pip/_internal/commands/__init__.py", line 96, in create_command module = importlib.import_module(module_path) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 986, in _gcd_import File "<frozen importlib._bootstrap>", line 969, in _find_and_load File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 673, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/pip/_internal/commands/search.py", line 18, in <module>

b5n 6y ago
I understand no one wants to deal with unexpected issues, especially when you're trying to get something done. Why not use virtual environments? You keep packages out of your system's python, and if you run into issues like above you can just recreate it: b5n:~/venv_dir$ python3 -m venv im_a_venv b5n:~/venv_dir$ . im_a_venv/bin/activate (im_a_venv)b5n:~/venv_dir$ pip install requests (im_a_venv)b5n:~/venv_dir$ pip freeze > requirements.txt (im_a_venv)b5n:~/venv_dir$ deactivate b5n:~/venv_dir$ python3 -m venv another_venv b5n:~/venv_dir$ . another_venv/bin/activate (another_venv)b@b5n:~/venv_dir$ pip install -r requirements.txt
- anonymousCar 6y ago
  While experienced python devs will say, yeah that'd how you should do it. The problem is that python by default isn't using virtualenvs. Consider rust or is where you need to specify global installs.
- iso1631 6y ago
  The reason I use linux and perl (or sometimes bash) - it just works, I get the least number of surprises. Dependencies in perl are handled by my OS same as everything else, I don't need to maintain multiple package managers, I just bash out the script and move on I don't write software as an end goal, I write software to accomplish my end goal.
elwell 6y ago
I spent 15 seconds trying to figure out how that 'Perl code' runs...

b5n 6y ago

I understand no one wants to deal with unexpected issues, especially when you're trying to get something done. Why not use virtual environments? You keep packages out of your system's python, and if you run into issues like above you can just recreate it: b5n:~/venv_dir$ python3 -m venv im_a_venv b5n:~/venv_dir$ . im_a_venv/bin/activate (im_a_venv)b5n:~/venv_dir$ pip install requests (im_a_venv)b5n:~/venv_dir$ pip freeze > requirements.txt (im_a_venv)b5n:~/venv_dir$ deactivate b5n:~/venv_dir$ python3 -m venv another_venv b5n:~/venv_dir$ . another_venv/bin/activate (another_venv)b@b5n:~/venv_dir$ pip install -r requirements.txt

anonymousCar 6y ago
While experienced python devs will say, yeah that'd how you should do it. The problem is that python by default isn't using virtualenvs. Consider rust or is where you need to specify global installs.
iso1631 6y ago
The reason I use linux and perl (or sometimes bash) - it just works, I get the least number of surprises. Dependencies in perl are handled by my OS same as everything else, I don't need to maintain multiple package managers, I just bash out the script and move on I don't write software as an end goal, I write software to accomplish my end goal.

elwell 6y ago

I spent 15 seconds trying to figure out how that 'Perl code' runs...