mmf-setup
=========
[![Documentation Status][rtd_badge]][rtd]
[![Tests][ci_badge]][ci]
[![codecov.io][codecov_badge]][codecov]
<!-- [![Language grade: Python][lgtm_mmf-setup_badge]][lgtm_mmf-setup] -->
<!-- [![Language grade: Python][lgtm_mmf-setup-fork_badge]][lgtm_mmf-setup-fork] -->
[![Pypi][PyPI_badge]][PyPI]
[![Python versions][PyPI_versions]][PyPI]
[![Code style: black][black_img]][black]
[](https://mybinder.org/v2/gh/forbes-group/mmf-setup/branch/default)
This meta-project provides an easy way to install all of the python tools I typically
use. It also serves as a fairly minimal example of setting up a package that [pip][] can
install, and specifying dependencies.
In particular, I structure it for the following use-cases:
1. Rapid installation and configuration of the tools I need. For example, I often use
[CoCalc][]. Whenever I create a new project, I need to perform some
initialization. With this project, it is simply a matter of using [pipx][] to install
this package, and then using some of the tools. Specifically:
```bash
pipx install mmf-setup
mmf_setup cocalc mercurial hg-evolve hg-git black
```
This does the following, and then links various configuration files to the home
directory:
```bash
pipx install mmf-setup
pipx inject mmf-setup mercurial hg-evolve hg-git black
curl -sSL https://install.python-poetry.org | python3 -
```
2. Initial setup of a python distribution on a new computer. This is a little more
involved since one needs to first install python (I recommend using
[Miniconda](http://conda.pydata.org/miniconda.html)) and then updating the tools.
3. A place to document various aspects of installing and setting up python and related
tools. Some of this is old, but kept here for reference.
4. A generic way of setting `sys.path` for development work using the following (in order
of decreasing precedence) by calling `mmf_setup.set_path()`.
- An entry in a `pyproject.toml` file somewhere in a higher-level directory.
- An entry in a `setup.cfg` file somewhere in a higher-level directory.
- The first parent directory with either of these files, a `setup.py` file, or `.hg`
or `.git` directories.
Quickstart (TL;DR)
==================
1. To get the notebook initialization features without having to install the package,
just copy [nbinit.py](nbinit.py) to your project. Importing this will try to execute
`import mmf_setup;mmf_setup.nbinit()` but failing this, will manually run a similar
code.
2. Install this package from the source directory,
[PyPI](https://pypi.python.org/pypi), etc. with one of the following:
- **Directly from PyPI**
```bash
python3 -m pip install --user mmf-setup[nbextensions]
```
- **From Source**
```bash
python3 -m pip install --user
hg+https://alum.mit.edu/www/mforbes/hg/forbes-group/mmf-setup[nbextensions]
```
- **From Local Source** *(Run this from the source directory after you unpack it.)*
```bash
python3 -m pip install --user .[nbextensions]
```
Note: these includes the `nbextensions` extra. You and run without the `--user` flag
if you want to install them system-wide rather than into [`site.USER_BASE`][].
3. To get the notebook tools for Jupyter (IPython) notebooks, execute the following as
a code cell in your notebook and then trust the notebook with `File/Trust Notebook`:
```python
import mmf_setup; mmf_setup.nbinit()
```
This will set the theme which is implemented in the output cell so it is stored for
use online such as when rendered through
[NBViewer](http://nbviewer.ipython.org). One can specify different
themes. (Presently only `theme='default'` and `theme='mmf'` are supported.)
4. **Mercurial:** If you want to install mercurial with the [hg-git][] and [Evolve][]
extensions, then you can do that with the `hg` extra:
```bash
python3 -m pip install --user .[hg]
```
This essentially runs `pip install mercurial hg-git hg-evolve`. You can then enable
these in your environment by sourcing the `mmf_setup` script in one of the following
ways:
```bash
eval $"(mmf_setup -v)" # Enable hg lg but not evolve, etc.
eval $"(mmf_setup -v -H)" # Enable evolve, etc.
mmf_setup -v [-H] # Shows what will be set set (dry run).
```
To do this automatically when you login, add this line to your `~/.bashc` or
`~/.bash_profile` scripts.
> **Warning:** the `eval $"(mmf_setup -v -H)"` option also includes a mercurial
> update hook which will add `%include ../.hgrc` to your projects `.hg/hgrc` file
> upon `hg > update`. This allows you to include project-specific mercurial
> customizations in your repository, but is a potential security risk. See the
> discussion below.
These can also be enabled manually by adding the following to your `~/.hgrc` file:
```ini
# ~/.hgrc
...
[extensions]
evolve =
topics =
hggit =
```
Setting `sys.path`
==================
The preferred way to work with python code is to install it, preferably into a virtual
environment or a conda environment. By installing it, you will assure that your program
or library is available to notebooks, etc. by being properly inserted into
sys.path. When developing, code, one can also do a ["editable"
installs](https://pip.pypa.io/en/stable/reference/pip_install/#local-project-installs)
with `python -m install -e \<path\>` so that code updates are seen.
When developing code, however, this may not meet all use-cases, so we provide
`mmf_utils.set_path(cwd='.')` which will set `mmf_setup.ROOT` and insert it at the start
of `sys.path`.
The algorithm for determining `ROOT` is as follows starting from `cwd` (which is `'.'`
by default, but can be specified in the call to `set_path()`). Note: in each case, the
specified path must be an existing directory or it will be ignored.
* A value specified as `mmf_setup.ROOT` will override everything.
* A value in the environmental variable `MMF_SETUP_ROOT` will override everything else.
* An explicit `ROOT` entry in the first `pyproject.toml` found:
```toml
# pyproject.toml
[tool.mmf_setup]
ROOT = 'src'
```
* An explict entry in the first `setup.cfg`:
```ini
# setup.cfg
[mmf_setup]
ROOT = src
```
* The first parent directory to contain any of the files `setup.py`, `setup.cfg`, or
`pyproject.toml`, or directories `.git`, or `.hg`.
If none of these yields a valid existing directory for `ROOT`, then it will not be set.
Mercurial (hg) Tools
====================
If you source the output of the `mmf_setup` script with one of the following:
```bash
eval $"(mmf_setup -v)"
eval $"(mmf_setup -v -H)"
```
then your `HGRCPATH` will be amended to include
[`hgrc.lga`](src/mmf_setup/_data/hgrc.lga) or
[`hgrc.full`](src/mmf_setup/_data/hgrc.full) respectively. The first adds a useful `hg
lga` (`hg lg` for short) command which provides a concise graphical display:
```bash
$ hg lg
@ 200:d michael (64 minutes ago) 0.4.0[0.4.0] tip
| ENH,DOC,TST,API: Cleaned up set_path...
o 199:d michael (31 hours ago) 0.4.0[0.4.0]
| WIP,CHK: Cleaning up set_path.
o 198:d michael (20 hours ago) 0.4.0[0.4.0]
| DOC: Added developer Notes.md
...
```
The second version with `-H` adds some useful extensions: [hg-git][], [Evolve][], and
enables [Topics][]. The latter are required, for example, to interface with
[Heptapod](https://octobus.net/blog/2019-09-04-heptapod-workflow.html).
Finally, the `-H` option enables an `hg update` hook, which adds `%include ../.hgrc` to
your project's `.hg/hgrc` file when you call `hg update`. This is a potential security
risk, because an untrusted repo could include dangerous commands in `.hgrc`. Thus, we
require user intervention before including this:
```bash
$ eval $"(mmf_setup -v -H)"
$ hg clone https://alum.mit.edu/www/mforbes/hg/forbes-group/mmf-setup
...
updating to branch default
88 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd mmf-setup
$ hg up 0.4.0
Repository .../mmf-setup contains an .hgrc file.
Including this in .hg/hgrc is a potential security risk.
Only do this if you trust the repository.
Include this .hgrc in .hg/hgrc? [yN]y
Adding '%include ../.hgrc' to '.hg/hgrc'
...
$ tail .hg/hgrc
...
%include ../.hgrc
```
CoCalc
======
We provide some tools for working on [CoCalc][]. To get started, simply do to the
following once you have enabled network access on your project by applying a license:
```bash
pipx install mmf-setup
mmf_setup cocalc
```
To see exactly what this will do, run:
```bash
mmf_setup cocalc -v
```
Once this is done, you should ensure that, whenever you use a terminal on [CoCalc][],
you appropriately set the following variables:
* `LC_HG_USERNAME`: Used by [mercurial][].
* `LC_GIT_USEREMAIL`, `LC_GIT_USERNAME`: Used by [git][].
These will identify you as you when you commit your work. (Needed, because all users
share the same project. See [cocalc#370][] for details.)
[cocalc#370]: <https://github.com/sagemathinc/cocalc/issues/370>
I recommend the following:
1. Forward these variables in your SSH config file (`~/.ssh/config`):
```
# ~/.ssh/config
Host cc-project1
User ff1cb986f...
Host cc*
HostName ssh.cocalc.com
ForwardAgent yes
SetEnv LC_HG_USERNAME=Your Full Name <your.email.address+hg@gmail.com>
SetEnv LC_GIT_USERNAME=Your Full Name
SetEnv LC_GIT_USEREMAIL=your.email.address+git@gmail.com
SetEnv LC_EDITOR=vi
```
The appropriate value for `User` can be found in the project Settings on [CoCalc][].
Optionally, use `SendEnv ...` and set these on your personal computer:
```bash
# ~/.bashrc or similar
LC_HG_USERNAME=Your Full Name <your.email.address+hg@gmail.com>
LC_GIT_USEREMAIL=your.email.address+git@gmail.com
LC_GIT_USERNAME=Your Full Name
```
2. If you want to run [Git][] or [Mercurial][] from the [CoCalc][] web interface, then
create a named terminal -- i.e. `Michael.term` -- and then set these variables in the
terminal startup script. (See https://doc.cocalc.com/terminal.html#startup-files for
details.)
[CoCalc]: <cocalc.com>
# Notes
See [Notes.md](Notes.md) for developer notes. Other notes about python, IPython,
etc. are stored in the [docs](docs) folder.
<!-- Badges -->
[rtd_badge]: <https://readthedocs.org/projects/mmf-setup/badge/?version=latest>
[rtd]: <https://mmf-setup.readthedocs.io/en/latest/?badge=latest>
[drone_badge]: <https://cloud.drone.io/api/badges/forbes-group/mmf-setup/status.svg>
[drone]: https://cloud.drone.io/forbes-group/mmf-setup
[ci_badge]: <https://github.com/mforbes/mmf-setup-fork/actions/workflows/tests.yml/badge.svg>
[ci]: <https://github.com/mforbes/mmf-setup-fork/actions/workflows/tests.yml>
[black]: https://github.com/psf/black
[black_img]: https://img.shields.io/badge/code%20style-black-000000.svg
[lgtm_mmf-setup-fork]: <https://lgtm.com/projects/g/mforbes/mmf-setup-fork/context:python>
[lgtm_mmf-setup-fork_badge]: <https://img.shields.io/lgtm/grade/python/g/mforbes/mmf-setup-fork.svg?logo=lgtm&logoWidth=18>
[lgtm_mmf-setup]: <https://lgtm.com/projects/g/forbes-group/mmf-setup/context:python>
[lgtm_mmf-setup_badge]: <https://img.shields.io/lgtm/grade/python/g/mforbes/mmf-setup.svg?logo=lgtm&logoWidth=18>
[codecov]: <https://codecov.io/github/mforbes/mmf-setup-fork/branch/default>
[codecov_badge]: <https://codecov.io/github/mforbes/mmf-setup-fork/coverage.svg?branch=default>
[PyPI_badge]: <https://img.shields.io/pypi/v/mmf-setup.svg>
[PyPI_versions]: <https://img.shields.io/pypi/pyversions/mmf-setup.svg>
[PyPI]: <https://pypi.python.org/pypi/mmf-setup> "mmf-setup on PyPI"
<!-- [](https://anaconda.org/conda-forge/jupytext) -->
<!-- Links -->
[Nox]: <https://nox.thea.codes> "Nox: Flexible test automation"
[Hypermodern Python]: <https://cjolowicz.github.io/posts/hypermodern-python-01-setup/>
"Hypermodern Python"
[`pyenv`]: <https://github.com/pyenv/pyenv> "Simple Python Version Management: pyenv"
[`minconda`]: <https://docs.conda.io/en/latest/miniconda.html> "Miniconda"
[Conda]: <https://docs.conda.io> "Conda"
[Heptapod]: <https://heptapod.net> "Heptapod website"
[pytest]: <https://docs.pytest.org> "pytest"
[pip]: <https://pip.pypa.io> "pip: the package installer for Python"
[pipx]: <https://pypa.github.io/pipx/>
"pipx: Install and Run Python Applications in Isolated Environments"
[`site.USER_BASE`]: <https://docs.python.org/3/library/site.html#site.USER_BASE>
[Evolve]: <https://www.mercurial-scm.org/doc/evolution/>
"Mercurial Evolve extension"
[Topics]: <https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html>
"Mercurial Topics tutorial"
[hg-git]: <https://hg-git.github.io>
[mercurial]: https://www.mercurial-scm.org/
[git]: https://git-scm.com/
Raw data
{
"_id": null,
"home_page": null,
"name": "mmf-setup",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "ipython, jupyter, notebook, setup, mercurial",
"author": null,
"author_email": "Michael McNeil Forbes <michael.forbes+python@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/79/bb/6e825f7e974ad08dc8e15ac4962c7ffdff253853199661fa8957470818f9/mmf_setup-0.4.12.tar.gz",
"platform": null,
"description": "mmf-setup\n=========\n\n[![Documentation Status][rtd_badge]][rtd]\n[![Tests][ci_badge]][ci]\n[![codecov.io][codecov_badge]][codecov]\n<!-- [![Language grade: Python][lgtm_mmf-setup_badge]][lgtm_mmf-setup] -->\n<!-- [![Language grade: Python][lgtm_mmf-setup-fork_badge]][lgtm_mmf-setup-fork] -->\n[![Pypi][PyPI_badge]][PyPI]\n[![Python versions][PyPI_versions]][PyPI]\n[![Code style: black][black_img]][black]\n[](https://mybinder.org/v2/gh/forbes-group/mmf-setup/branch/default)\n\nThis meta-project provides an easy way to install all of the python tools I typically\nuse. It also serves as a fairly minimal example of setting up a package that [pip][] can\ninstall, and specifying dependencies.\n\nIn particular, I structure it for the following use-cases:\n\n1. Rapid installation and configuration of the tools I need. For example, I often use\n [CoCalc][]. Whenever I create a new project, I need to perform some\n initialization. With this project, it is simply a matter of using [pipx][] to install\n this package, and then using some of the tools. Specifically:\n\n ```bash\n pipx install mmf-setup\n mmf_setup cocalc mercurial hg-evolve hg-git black\n ```\n \n This does the following, and then links various configuration files to the home\n directory:\n \n ```bash\n pipx install mmf-setup\n pipx inject mmf-setup mercurial hg-evolve hg-git black\n curl -sSL https://install.python-poetry.org | python3 -\n ```\n\n2. Initial setup of a python distribution on a new computer. This is a little more\n involved since one needs to first install python (I recommend using\n [Miniconda](http://conda.pydata.org/miniconda.html)) and then updating the tools.\n3. A place to document various aspects of installing and setting up python and related\n tools. Some of this is old, but kept here for reference.\n4. A generic way of setting `sys.path` for development work using the following (in order\n of decreasing precedence) by calling `mmf_setup.set_path()`.\n - An entry in a `pyproject.toml` file somewhere in a higher-level directory.\n - An entry in a `setup.cfg` file somewhere in a higher-level directory.\n - The first parent directory with either of these files, a `setup.py` file, or `.hg`\n or `.git` directories.\n\nQuickstart (TL;DR)\n==================\n\n1. To get the notebook initialization features without having to install the package,\n just copy [nbinit.py](nbinit.py) to your project. Importing this will try to execute\n `import mmf_setup;mmf_setup.nbinit()` but failing this, will manually run a similar\n code.\n2. Install this package from the source directory,\n [PyPI](https://pypi.python.org/pypi), etc. with one of the following:\n\n - **Directly from PyPI**\n\n ```bash\n python3 -m pip install --user mmf-setup[nbextensions]\n ```\n - **From Source**\n ```bash\n python3 -m pip install --user\n hg+https://alum.mit.edu/www/mforbes/hg/forbes-group/mmf-setup[nbextensions]\n ```\n\n - **From Local Source** *(Run this from the source directory after you unpack it.)*\n\n ```bash\n python3 -m pip install --user .[nbextensions]\n ```\n\n Note: these includes the `nbextensions` extra. You and run without the `--user` flag\n if you want to install them system-wide rather than into [`site.USER_BASE`][].\n\n3. To get the notebook tools for Jupyter (IPython) notebooks, execute the following as\n a code cell in your notebook and then trust the notebook with `File/Trust Notebook`:\n\n ```python\n import mmf_setup; mmf_setup.nbinit()\n ```\n\n This will set the theme which is implemented in the output cell so it is stored for\n use online such as when rendered through\n [NBViewer](http://nbviewer.ipython.org). One can specify different\n themes. (Presently only `theme='default'` and `theme='mmf'` are supported.)\n\n4. **Mercurial:** If you want to install mercurial with the [hg-git][] and [Evolve][]\n extensions, then you can do that with the `hg` extra:\n\n ```bash\n python3 -m pip install --user .[hg]\n ```\n\n This essentially runs `pip install mercurial hg-git hg-evolve`. You can then enable\n these in your environment by sourcing the `mmf_setup` script in one of the following\n ways:\n\n ```bash\n eval $\"(mmf_setup -v)\" # Enable hg lg but not evolve, etc.\n eval $\"(mmf_setup -v -H)\" # Enable evolve, etc.\n mmf_setup -v [-H] # Shows what will be set set (dry run).\n ```\n\n To do this automatically when you login, add this line to your `~/.bashc` or\n `~/.bash_profile` scripts.\n \n > **Warning:** the `eval $\"(mmf_setup -v -H)\"` option also includes a mercurial\n > update hook which will add `%include ../.hgrc` to your projects `.hg/hgrc` file\n > upon `hg > update`. This allows you to include project-specific mercurial\n > customizations in your repository, but is a potential security risk. See the\n > discussion below.\n\n These can also be enabled manually by adding the following to your `~/.hgrc` file:\n\n ```ini\n # ~/.hgrc\n ...\n [extensions]\n evolve =\n topics =\n hggit =\n ```\n\nSetting `sys.path`\n==================\n\nThe preferred way to work with python code is to install it, preferably into a virtual\nenvironment or a conda environment. By installing it, you will assure that your program\nor library is available to notebooks, etc. by being properly inserted into\nsys.path. When developing, code, one can also do a [\"editable\"\ninstalls](https://pip.pypa.io/en/stable/reference/pip_install/#local-project-installs)\nwith `python -m install -e \\<path\\>` so that code updates are seen.\n\nWhen developing code, however, this may not meet all use-cases, so we provide\n`mmf_utils.set_path(cwd='.')` which will set `mmf_setup.ROOT` and insert it at the start\nof `sys.path`. \n\nThe algorithm for determining `ROOT` is as follows starting from `cwd` (which is `'.'`\nby default, but can be specified in the call to `set_path()`). Note: in each case, the\nspecified path must be an existing directory or it will be ignored.\n\n* A value specified as `mmf_setup.ROOT` will override everything.\n* A value in the environmental variable `MMF_SETUP_ROOT` will override everything else.\n* An explicit `ROOT` entry in the first `pyproject.toml` found:\n \n ```toml\n # pyproject.toml\n [tool.mmf_setup]\n ROOT = 'src'\n ```\n* An explict entry in the first `setup.cfg`:\n \n ```ini\n # setup.cfg\n [mmf_setup]\n ROOT = src\n ```\n* The first parent directory to contain any of the files `setup.py`, `setup.cfg`, or\n `pyproject.toml`, or directories `.git`, or `.hg`.\n\nIf none of these yields a valid existing directory for `ROOT`, then it will not be set.\n\nMercurial (hg) Tools\n====================\n\nIf you source the output of the `mmf_setup` script with one of the following:\n\n```bash\neval $\"(mmf_setup -v)\"\neval $\"(mmf_setup -v -H)\"\n```\n\nthen your `HGRCPATH` will be amended to include\n[`hgrc.lga`](src/mmf_setup/_data/hgrc.lga) or\n[`hgrc.full`](src/mmf_setup/_data/hgrc.full) respectively. The first adds a useful `hg\nlga` (`hg lg` for short) command which provides a concise graphical display:\n\n```bash\n$ hg lg\n@ 200:d michael (64 minutes ago) 0.4.0[0.4.0] tip\n| ENH,DOC,TST,API: Cleaned up set_path...\no 199:d michael (31 hours ago) 0.4.0[0.4.0]\n| WIP,CHK: Cleaning up set_path.\no 198:d michael (20 hours ago) 0.4.0[0.4.0]\n| DOC: Added developer Notes.md\n...\n```\n\nThe second version with `-H` adds some useful extensions: [hg-git][], [Evolve][], and\nenables [Topics][]. The latter are required, for example, to interface with\n[Heptapod](https://octobus.net/blog/2019-09-04-heptapod-workflow.html).\n\nFinally, the `-H` option enables an `hg update` hook, which adds `%include ../.hgrc` to\nyour project's `.hg/hgrc` file when you call `hg update`. This is a potential security\nrisk, because an untrusted repo could include dangerous commands in `.hgrc`. Thus, we\nrequire user intervention before including this:\n\n```bash\n$ eval $\"(mmf_setup -v -H)\"\n$ hg clone https://alum.mit.edu/www/mforbes/hg/forbes-group/mmf-setup\n...\nupdating to branch default\n88 files updated, 0 files merged, 0 files removed, 0 files unresolved\n$ cd mmf-setup\n$ hg up 0.4.0\nRepository .../mmf-setup contains an .hgrc file.\nIncluding this in .hg/hgrc is a potential security risk.\nOnly do this if you trust the repository.\n\nInclude this .hgrc in .hg/hgrc? [yN]y\nAdding '%include ../.hgrc' to '.hg/hgrc'\n...\n$ tail .hg/hgrc\n...\n%include ../.hgrc\n```\n\nCoCalc\n======\n\nWe provide some tools for working on [CoCalc][]. To get started, simply do to the\nfollowing once you have enabled network access on your project by applying a license:\n\n```bash\npipx install mmf-setup\nmmf_setup cocalc\n```\n\nTo see exactly what this will do, run:\n\n```bash\nmmf_setup cocalc -v\n```\n\nOnce this is done, you should ensure that, whenever you use a terminal on [CoCalc][],\nyou appropriately set the following variables:\n\n* `LC_HG_USERNAME`: Used by [mercurial][].\n* `LC_GIT_USEREMAIL`, `LC_GIT_USERNAME`: Used by [git][].\n\nThese will identify you as you when you commit your work. (Needed, because all users\nshare the same project. See [cocalc#370][] for details.)\n\n[cocalc#370]: <https://github.com/sagemathinc/cocalc/issues/370>\n\nI recommend the following:\n\n1. Forward these variables in your SSH config file (`~/.ssh/config`):\n\n ```\n # ~/.ssh/config\n Host cc-project1\n User ff1cb986f...\n \n Host cc*\n HostName ssh.cocalc.com\n ForwardAgent yes\n SetEnv LC_HG_USERNAME=Your Full Name <your.email.address+hg@gmail.com>\n SetEnv LC_GIT_USERNAME=Your Full Name\n SetEnv LC_GIT_USEREMAIL=your.email.address+git@gmail.com\n SetEnv LC_EDITOR=vi\n ```\n \n The appropriate value for `User` can be found in the project Settings on [CoCalc][].\n \n Optionally, use `SendEnv ...` and set these on your personal computer:\n\n ```bash\n # ~/.bashrc or similar\n LC_HG_USERNAME=Your Full Name <your.email.address+hg@gmail.com>\n LC_GIT_USEREMAIL=your.email.address+git@gmail.com\n LC_GIT_USERNAME=Your Full Name\n ```\n\n2. If you want to run [Git][] or [Mercurial][] from the [CoCalc][] web interface, then\n create a named terminal -- i.e. `Michael.term` -- and then set these variables in the\n terminal startup script. (See https://doc.cocalc.com/terminal.html#startup-files for\n details.)\n \n[CoCalc]: <cocalc.com>\n\n# Notes\n\nSee [Notes.md](Notes.md) for developer notes. Other notes about python, IPython,\netc. are stored in the [docs](docs) folder. \n\n\n<!-- Badges -->\n[rtd_badge]: <https://readthedocs.org/projects/mmf-setup/badge/?version=latest>\n[rtd]: <https://mmf-setup.readthedocs.io/en/latest/?badge=latest>\n\n\n[drone_badge]: <https://cloud.drone.io/api/badges/forbes-group/mmf-setup/status.svg>\n[drone]: https://cloud.drone.io/forbes-group/mmf-setup\n[ci_badge]: <https://github.com/mforbes/mmf-setup-fork/actions/workflows/tests.yml/badge.svg>\n[ci]: <https://github.com/mforbes/mmf-setup-fork/actions/workflows/tests.yml>\n\n[black]: https://github.com/psf/black\n[black_img]: https://img.shields.io/badge/code%20style-black-000000.svg\n\n\n[lgtm_mmf-setup-fork]: <https://lgtm.com/projects/g/mforbes/mmf-setup-fork/context:python>\n[lgtm_mmf-setup-fork_badge]: <https://img.shields.io/lgtm/grade/python/g/mforbes/mmf-setup-fork.svg?logo=lgtm&logoWidth=18>\n\n[lgtm_mmf-setup]: <https://lgtm.com/projects/g/forbes-group/mmf-setup/context:python>\n[lgtm_mmf-setup_badge]: <https://img.shields.io/lgtm/grade/python/g/mforbes/mmf-setup.svg?logo=lgtm&logoWidth=18> \n\n[codecov]: <https://codecov.io/github/mforbes/mmf-setup-fork/branch/default>\n[codecov_badge]: <https://codecov.io/github/mforbes/mmf-setup-fork/coverage.svg?branch=default>\n\n[PyPI_badge]: <https://img.shields.io/pypi/v/mmf-setup.svg>\n[PyPI_versions]: <https://img.shields.io/pypi/pyversions/mmf-setup.svg>\n[PyPI]: <https://pypi.python.org/pypi/mmf-setup> \"mmf-setup on PyPI\"\n\n<!-- [](https://anaconda.org/conda-forge/jupytext) -->\n<!-- Links -->\n[Nox]: <https://nox.thea.codes> \"Nox: Flexible test automation\"\n[Hypermodern Python]: <https://cjolowicz.github.io/posts/hypermodern-python-01-setup/> \n \"Hypermodern Python\"\n[`pyenv`]: <https://github.com/pyenv/pyenv> \"Simple Python Version Management: pyenv\"\n[`minconda`]: <https://docs.conda.io/en/latest/miniconda.html> \"Miniconda\"\n[Conda]: <https://docs.conda.io> \"Conda\"\n[Heptapod]: <https://heptapod.net> \"Heptapod website\"\n[pytest]: <https://docs.pytest.org> \"pytest\"\n[pip]: <https://pip.pypa.io> \"pip: the package installer for Python\"\n[pipx]: <https://pypa.github.io/pipx/>\n \"pipx: Install and Run Python Applications in Isolated Environments\"\n[`site.USER_BASE`]: <https://docs.python.org/3/library/site.html#site.USER_BASE>\n[Evolve]: <https://www.mercurial-scm.org/doc/evolution/> \n \"Mercurial Evolve extension\"\n[Topics]: <https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html> \n \"Mercurial Topics tutorial\"\n[hg-git]: <https://hg-git.github.io>\n[mercurial]: https://www.mercurial-scm.org/\n[git]: https://git-scm.com/\n",
"bugtrack_url": null,
"license": "BSD-3-Clause",
"summary": "Meta-package to quickly initialize my python environment.",
"version": "0.4.12",
"project_urls": null,
"split_keywords": [
"ipython",
" jupyter",
" notebook",
" setup",
" mercurial"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "d9d46752558d8f7e69aa26d15f391b4c2b7ba1dea202ce4bfa40ba6ac3f4d741",
"md5": "22456b03db0daac3715c5a692675ef63",
"sha256": "6d5de73172352997b42fdc04cd4b4c075643d72e5cc3d352387d366076194137"
},
"downloads": -1,
"filename": "mmf_setup-0.4.12-py3-none-any.whl",
"has_sig": false,
"md5_digest": "22456b03db0daac3715c5a692675ef63",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 60301,
"upload_time": "2024-03-22T22:52:33",
"upload_time_iso_8601": "2024-03-22T22:52:33.735718Z",
"url": "https://files.pythonhosted.org/packages/d9/d4/6752558d8f7e69aa26d15f391b4c2b7ba1dea202ce4bfa40ba6ac3f4d741/mmf_setup-0.4.12-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "79bb6e825f7e974ad08dc8e15ac4962c7ffdff253853199661fa8957470818f9",
"md5": "9a644283a04c2218254eba976b1af344",
"sha256": "6ea3835a9c43a128fbdb1cce90e23ec5c36db7cacca0a9c0a243c8ade27bb499"
},
"downloads": -1,
"filename": "mmf_setup-0.4.12.tar.gz",
"has_sig": false,
"md5_digest": "9a644283a04c2218254eba976b1af344",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 131375,
"upload_time": "2024-03-22T22:52:40",
"upload_time_iso_8601": "2024-03-22T22:52:40.025887Z",
"url": "https://files.pythonhosted.org/packages/79/bb/6e825f7e974ad08dc8e15ac4962c7ffdff253853199661fa8957470818f9/mmf_setup-0.4.12.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-22 22:52:40",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "mmf-setup"
}
JSON