using the bare Windows command line), it’s unlikely that pip will work. Note: If you’re following these instructions outside of WSL (e.g. They actually provide a requirements.txt but I couldn’t get it to work so not sure what was up with that, I didn’t really try to debug at all. You’ll need to install a couple dependencies, run the following in your command line: pip install requests Feel free to pick another if you like, Chocolatey is just the one that was recommended to me so it’s what I use. There are certainly other package managers available for Windows, including an official one that they released since the most recent time I set up a Windows installation. They have some additional instructions there.You need to give the PowerShell prompt Administrator access. It’s a POWERSHELL SCRIPT designed to work in POWERSHELL ONLY. It WILL NOT WORK if you paste it into the Command Prompt, Git Bash, WSL, etc. You MUST paste the command into WINDOWS POWERSHELL.Scroll past this and accept the “Individual” option. There’s a couple installation options.This will take care of all of the PATH shit for you and also give you pip and stuff without you having to worry. To install Python in Windows, my preferred method is first to install the package manager Chocolatey and then run choco install python. (Note that if you’re reading this post more than 6-ish months after publication, my instructions may be outdated, so if something doesn’t work keep that in mind.) Getting Python However I will also provide my own instructions. While I did redo my entire PWB installation as I was writing this post, it’s always possible I left out a minor but important step or made a typo or something, so please let me know if anything doesn’t work as advertised - I’ll help you troubleshoot and update as needed! Pywikibot Getting PWB And then maybe come back to this later!Īlso, you will have to edit some of the source code of PWB to workaround a couple things where it doesn’t play nice with WSL. If not, and you don’t want to use this tool, that’s okay! Check out AutoWikiBrowser instead, a GUI-based tool that can accomplish some of the same things PWB can (though it is admittedly significantly more limited in scope). I assume you’re familiar with commands like cd and ls already, and with the general concept of typing things into a terminal and having things happen, since that’s how PWB works. Lets you set aliases incredibly easily, which work from any directory, without adding anything to PATHĪs a warning, if you aren’t comfortable with command-line operations, you’ll probably have a very uncomfortable time with this and hate every minute of it.Doesn’t lag for like 10 seconds when you press ctrl+C in the middle of a batch job omg.Allows you to manage and clear said history as needed if you have unwanted suggestions.Remembers your command history and suggests autocompletions.Has color highlighting including things like matched/unmatched quotes.There’s a number of QOL improvements over the standard Windows command prompt, including it: In this post I’ll first go over how to install and configure PWB for third-party (non-WMF) wikis (I actually reinstalled/updated PWB for the first time in three years just to write this), and then I’ll show you how to set up Windows Subsystem for Linux with the Fish shell. It’s made even better by running it in a shell that doesn’t suck, which unfortunately does not include the Windows command prompt. Pywikibot is a set of command-line tools written in Python that can be invaluable when performing administration tasks on wikis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |