You can install bash on windows. (GoW, Cygwin, Ming), but Docker (and,
soon, runC OCP 1.0) is probably your best bet for maximum compatibility
with most {python, open source} tutorials. Installing the code as non-root
is a good idea (e.g. with a .zip or a .tar.gz or a Python .whl wheel)
I think the bash $ and # PS1 should be fairly easy to differentiate from
unprefixed expressions. IDK if those are the POSIX defaults.
These list {Linux,Mac} when Windows is not supported:
https://docs.continuum.io/anaconda/pkg-docs
.rst/ReStructuredText: code directive
.. code:: bash
# Check out the switches for ifconfig/ipconfig /h.
.. code:: python
"""PowerShell is open source now"""
.md/Markdown: fenced code block
```bash
bash --version
help declare -r
```
```python
python -v
```
On Thursday, September 15, 2016, Thomas Kluyver <tho...@kluyver.me.uk>
wrote:
> On Thu, Sep 15, 2016, at 01:53 PM, Wes Turner wrote:
>
> Shell commands can/could/should be clearly indicated with a '$' prefix:
>
> $ python -m pip install numpy
>
>
> That's a common convention, but:
>
> - It comes from POSIX platforms where the default prompt ends in $. The
> default prompt in Windows ends with >, so $ is not clear.
> - On all platforms, new users may well not recognise that convention.
> - Users may think they have to type the $ as part of the command, leading
> to even more confusion.
>
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
