Skip to content
GitLab
Commit 288d6c90 authored by Paul McCarthy's avatar Paul McCarthy 🚵
Browse files

Merge branch 'mnt/structuring' into 'master' 

Mnt/structuring

See merge request fsl/pytreat-practicals-2020!19
parents 561f8629 31fcc2e6
Hide whitespace changes
Inline Side-by-side
talks/structuring/structuring.ipynb → advanced_topics/09_structuring_projects.ipynb
View file @ 288d6c90
......@@ -19,15 +19,15 @@
"\n",
"\n",
"* [Recommended project structure](#recommended-project-structure)\n",
" * [The `mypackage/` directory](#the-mypackage-directory)\n",
" * [`README`](#readme)\n",
" * [`LICENSE`](#license)\n",
" * [`requirements.txt`](#requirements-txt)\n",
" * [`setup.py`](#setup-py)\n",
" * [The `mypackage/` directory](#the-mypackage-directory)\n",
" * [`README`](#readme)\n",
" * [`LICENSE`](#license)\n",
" * [`requirements.txt`](#requirements-txt)\n",
" * [`setup.py`](#setup-py)\n",
"* [Appendix: Tests](#appendix-tests)\n",
"* [Appendix: Versioning](#appendix-versioning)\n",
" * [Include the version in your code](#include-the-version-in-your-code)\n",
" * [Deprecate, don't remove!](#deprecate-dont-remove)\n",
" * [Include the version in your code](#include-the-version-in-your-code)\n",
" * [Deprecate, don't remove!](#deprecate-dont-remove)\n",
"* [Appendix: Cookiecutter](#appendix-cookiecutter)\n",
"\n",
"\n",
......@@ -65,7 +65,7 @@
"\n",
"The first thing you should do is make sure that all of your python code is\n",
"organised into a sensibly-named\n",
"[_package_](https://docs.python.org/3.5/tutorial/modules.html#packages). This\n",
"[*package*](https://docs.python.org/3/tutorial/modules.html#packages). This\n",
"is important, because it greatly reduces the possibility of naming collisions\n",
"when people install your library alongside other libraries. Hands up those of\n",
"you who have ever written a file called `utils.[py|m|c|cpp]`!\n",
......@@ -106,10 +106,12 @@
"that your project requires. For example:\n",
"\n",
"\n",
"> six==1.*\n",
"> numpy==1.*\n",
"> scipy>=0.18,<2\n",
"> nibabel==2.*\n",
"> ```\n",
"> six==1.*\n",
"> numpy==1.*\n",
"> scipy>=0.18\n",
"> nibabel==2.*\n",
"> ```\n",
"\n",
"\n",
"If your project has optional dependencies, i.e. libraries which are not\n",
......@@ -122,7 +124,9 @@
"others to install the dependencies needed by your project, simply by running:\n",
"\n",
"\n",
"> pip install -r requirements.txt\n",
"> ```\n",
"> pip install -r requirements.txt\n",
"> ```\n",
"\n",
"\n",
"<a class=\"anchor\" id=\"setup-py\"></a>\n",
......@@ -174,7 +178,7 @@
">\n",
"> name='Example project',\n",
"> description='Example Python project for PyTreat',\n",
"> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals/',\n",
"> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020/',\n",
"> author='Paul McCarthy',\n",
"> author_email='pauldmccarthy@gmail.com',\n",
"> license='Apache License Version 2.0',\n",
......@@ -220,7 +224,7 @@
"right?). There are two main conventions:\n",
"\n",
"\n",
"You can store your test files _inside_ your package directory:\n",
"You can store your test files *inside* your package directory:\n",
"\n",
"\n",
"> ```\n",
......@@ -234,8 +238,7 @@
"> ```\n",
"\n",
"\n",
"\n",
"Or, you can store your test files _alongside_ your package directory:\n",
"Or, you can store your test files *alongside* your package directory:\n",
"\n",
"\n",
"> ```\n",
......@@ -267,7 +270,7 @@
"\n",
"If you are intending to make your project available for public use (e.g. on\n",
"[PyPI](https://pypi.python.org/pypi) and/or\n",
"[conda](https://anaconda.org/anaconda/repo)), it is __very important__ to\n",
"[conda](https://anaconda.org/anaconda/repo)), it is **very important** to\n",
"manage the version number of your project. If somebody decides to build their\n",
"software on top of your project, they are not going to be very happy with you\n",
"if you make substantial, API-breaking changes without changing your version\n",
......@@ -277,11 +280,13 @@
"Python has [official standards](https://www.python.org/dev/peps/pep-0440/) on\n",
"what constitutes a valid version number. These standards can be quite\n",
"complicated but, in the vast majority of cases, a simple three-number\n",
"versioning scheme comprising _major_, _minor_, and _patch_ release\n",
"versioning scheme comprising *major*, *minor*, and *patch* release\n",
"numbers should suffice. Such a version number has the form:\n",
"\n",
"\n",
"> major.minor.patch\n",
"> ```\n",
"> major.minor.patch\n",
"> ```\n",
"\n",
"\n",
"For example, a version number of `1.3.2` has a _major_ release of 1, _minor_\n",
......@@ -291,25 +296,25 @@
"If you follow some simple and rational guidelines for versioning\n",
"`your_project`, then people who use your project can, for instance, specify\n",
"that they depend on `your_project==1.*`, and be sure that their code will work\n",
"for _any_ version of `your_project` with a major release of 1. Following these\n",
"for *any* version of `your_project` with a major release of 1. Following these\n",
"simple guidelines greatly improves software interoperability, and makes\n",
"everybody (i.e. developers of other projects, and end users) much happier!\n",
"\n",
"\n",
"Many modern Python projects use some form of [_semantic\n",
"versioning_](https://semver.org/). Semantic versioning is simply a set of\n",
"Many modern Python projects use some form of [*semantic\n",
"versioning*](https://semver.org/). Semantic versioning is simply a set of\n",
"guidelines on how to manage your version number:\n",
"\n",
"\n",
" - The _major_ release number should be incremented whenever you introduce any\n",
" - The *major* release number should be incremented whenever you introduce any\n",
" backwards-incompatible changes. In other words, if you change your code\n",
" such that some other code which uses your code would break, you should\n",
" increment the major release number.\n",
"\n",
" - The _minor_ release number should be incremented whenever you add any new\n",
" - The *minor* release number should be incremented whenever you add any new\n",
" (backwards-compatible) features to your project.\n",
"\n",
" - The _patch_ release number should be incremented for backwards-compatible\n",
" - The *patch* release number should be incremented for backwards-compatible\n",
" bug-fixes and other minor changes.\n",
"\n",
"\n",
......@@ -328,7 +333,9 @@
"our `example_project/mypackage/__init__.py` file contains this line:\n",
"\n",
"\n",
"> __version__ = '0.1.0'\n",
"> ```\n",
"> __version__ = '0.1.0'\n",
"> ```\n",
"\n",
"\n",
"This makes a library's version number programmatically accessible and\n",
......@@ -341,7 +348,7 @@
"\n",
"If you really want to change your API, but can't bring yourself to increment\n",
"your major release number, consider\n",
"[_deprecating_](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)\n",
"[*deprecating*](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)\n",
"the old API, and postponing its removal until you are ready for a major\n",
"release. This will allow you to change your API, but retain\n",
"backwards-compatilbiity with the old API until it can safely be removed at the\n",
......
%% Cell type:markdown id: tags:
# Structuring a Python project
If you are writing code that you are sure will never be seen or used by
anybody else, then you can structure your project however you want, and you
can stop reading now.
However, if you are intending to make your code available for others to use,
either as end users, or as a dependency of their own code, you will make their
lives much easier if you spend a little time organising your project
directory.
* [Recommended project structure](#recommended-project-structure)
* [The `mypackage/` directory](#the-mypackage-directory)
* [`README`](#readme)
* [`LICENSE`](#license)
* [`requirements.txt`](#requirements-txt)
* [`setup.py`](#setup-py)
* [The `mypackage/` directory](#the-mypackage-directory)
* [`README`](#readme)
* [`LICENSE`](#license)
* [`requirements.txt`](#requirements-txt)
* [`setup.py`](#setup-py)
* [Appendix: Tests](#appendix-tests)
* [Appendix: Versioning](#appendix-versioning)
* [Include the version in your code](#include-the-version-in-your-code)
* [Deprecate, don't remove!](#deprecate-dont-remove)
* [Include the version in your code](#include-the-version-in-your-code)
* [Deprecate, don't remove!](#deprecate-dont-remove)
* [Appendix: Cookiecutter](#appendix-cookiecutter)
Official documentation:
https://packaging.python.org/tutorials/distributing-packages/
<a class="anchor" id="recommended-project-structure"></a>
## Recommended project structure
A Python project directory should, at the very least, have a structure that
resembles the following:
> ```
> myproject/
> mypackage/
> __init__.py
> mymodule.py
> README
> LICENSE
> requirements.txt
> setup.py
> ```
This example structure is in the `example_project/` sub-directory - have a
look through it if you like.
<a class="anchor" id="the-mypackage-directory"></a>
### The `mypackage/` directory
The first thing you should do is make sure that all of your python code is
organised into a sensibly-named
[_package_](https://docs.python.org/3.5/tutorial/modules.html#packages). This
[*package*](https://docs.python.org/3/tutorial/modules.html#packages). This
is important, because it greatly reduces the possibility of naming collisions
when people install your library alongside other libraries. Hands up those of
you who have ever written a file called `utils.[py|m|c|cpp]`!
Check out the `advanced_topics/02_modules_and_packages.ipynb` practical for
more details on packages in Python.
<a class="anchor" id="readme"></a>
### `README`
Every project should have a README file. This is simply a plain text file
which describes your project and how to use it. It is common and acceptable
for a README file to be written in plain text,
[reStructuredText](http://www.sphinx-doc.org/en/stable/rest.html)
(`README.rst`), or
[markdown](https://guides.github.com/features/mastering-markdown/)
(`README.md`).
<a class="anchor" id="license"></a>
### `LICENSE`
Having a LICENSE file makes it easy for people to understand the constraints
under which your code can be used.
<a class="anchor" id="requirements-txt"></a>
### `requirements.txt`
This file is not strictly necessary, but is very common in Python projects.
It contains a list of the Python-based dependencies of your project, in a
standardised syntax. You can specify the exact version, or range of versions,
that your project requires. For example:
> six==1.*
> numpy==1.*
> scipy>=0.18,<2
> nibabel==2.*
> ```
> six==1.*
> numpy==1.*
> scipy>=0.18
> nibabel==2.*
> ```
If your project has optional dependencies, i.e. libraries which are not
critical but, if present, will allow your project to offer some extra
features, you can list them in a separate requirements file called, for
example, `requirements-extra.txt`.
Having all your dependencies listed in a file in this way makes it easy for
others to install the dependencies needed by your project, simply by running:
> pip install -r requirements.txt
> ```
> pip install -r requirements.txt
> ```
<a class="anchor" id="setup-py"></a>
### `setup.py`
This is the most important file (apart from your code, of course). Python
projects are installed using
[`setuptools`](https://setuptools.readthedocs.io/en/latest/), which is used
internally during both the creation of, and installation of Python libraries.
The `setup.py` file in a Python project is akin to a `Makefile` in a C/C++
project. But `setup.py` is also the location where you can define project
metadata (e.g. name, author, URL, etc) in a standardised format and, if
necessary, customise aspects of the build process for your library.
You generally don't need to worry about, or interact with `setuptools` at all.
With one exception - `setup.py` is a Python script, and its main job is to
call the `setuptools.setup` function, passing it information about your
project.
The `setup.py` for our example project might look like this:
> ```
> #!/usr/bin/env python
>
> from setuptools import setup
> from setuptools import find_packages
>
> # Import version number from
> # the project package (see
> # the section on versioning).
> from mypackage import __version__
>
> # Read in requirements from
> # the requirements.txt file.
> with open('requirements.txt', 'rt') as f:
> requirements = [l.strip() for l in f.readlines()]
>
> # Generate a list of all of the
> # packages that are in your project.
> packages = find_packages()
>
> setup(
>
> name='Example project',
> description='Example Python project for PyTreat',
> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals/',
> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020/',
> author='Paul McCarthy',
> author_email='pauldmccarthy@gmail.com',
> license='Apache License Version 2.0',
>
> packages=packages,
>
> version=__version__,
>
> install_requires=requirements,
>
> classifiers=[
> 'Development Status :: 3 - Alpha',
> 'Intended Audience :: Developers',
> 'License :: OSI Approved :: Apache Software License',
> 'Programming Language :: Python :: 2.7',
> 'Programming Language :: Python :: 3.4',
> 'Programming Language :: Python :: 3.5',
> 'Programming Language :: Python :: 3.6',
> 'Topic :: Software Development :: Libraries :: Python Modules'],
> )
> ```
The `setup` function gets passed all of your project's metadata, including its
version number, depedencies, and licensing information. The `classifiers`
argument should contain a list of
[classifiers](https://pypi.python.org/pypi?%3Aaction=list_classifiers) which
are applicable to your project. Classifiers are purely for descriptive
purposes - they can be used to aid people in finding your project on
[`PyPI`](https://pypi.python.org/pypi), if you release it there.
See
[here](https://packaging.python.org/tutorials/distributing-packages/#setup-args)
for more details on `setup.py` and the `setup` function.
<a class="anchor" id="appendix-tests"></a>
## Appendix: Tests
There are no strict rules for where to put your tests (you have tests,
right?). There are two main conventions:
You can store your test files _inside_ your package directory:
You can store your test files *inside* your package directory:
> ```
> myproject/
> mypackage/
> __init__.py
> mymodule.py
> tests/
> __init__.py
> test_mymodule.py
> ```
Or, you can store your test files _alongside_ your package directory:
Or, you can store your test files *alongside* your package directory:
> ```
> myproject/
> mypackage/
> __init__.py
> mymodule.py
> tests/
> test_mymodule.py
> ```
If you want your test code to be completely independent of your project's
code, then go with the second option. However, if you would like your test
code to be distributed as part of your project (e.g. so that end users can run
them), then the first option is probably the best.
But in the end, the standard Python unit testing frameworks
([`pytest`](https://docs.pytest.org/en/latest/) and
[`nose`](http://nose2.readthedocs.io/en/latest/)) are pretty good at finding
your test functions no matter where you've hidden them, so the choice is
really up to you.
<a class="anchor" id="appendix-versioning"></a>
## Appendix: Versioning
If you are intending to make your project available for public use (e.g. on
[PyPI](https://pypi.python.org/pypi) and/or
[conda](https://anaconda.org/anaconda/repo)), it is __very important__ to
[conda](https://anaconda.org/anaconda/repo)), it is **very important** to
manage the version number of your project. If somebody decides to build their
software on top of your project, they are not going to be very happy with you
if you make substantial, API-breaking changes without changing your version
number in an appropriate manner.
Python has [official standards](https://www.python.org/dev/peps/pep-0440/) on
what constitutes a valid version number. These standards can be quite
complicated but, in the vast majority of cases, a simple three-number
versioning scheme comprising _major_, _minor_, and _patch_ release
versioning scheme comprising *major*, *minor*, and *patch* release
numbers should suffice. Such a version number has the form:
> major.minor.patch
> ```
> major.minor.patch
> ```
For example, a version number of `1.3.2` has a _major_ release of 1, _minor_
release of 3, and a _patch_ release of 2.
If you follow some simple and rational guidelines for versioning
`your_project`, then people who use your project can, for instance, specify
that they depend on `your_project==1.*`, and be sure that their code will work
for _any_ version of `your_project` with a major release of 1. Following these
for *any* version of `your_project` with a major release of 1. Following these
simple guidelines greatly improves software interoperability, and makes
everybody (i.e. developers of other projects, and end users) much happier!
Many modern Python projects use some form of [_semantic
versioning_](https://semver.org/). Semantic versioning is simply a set of
Many modern Python projects use some form of [*semantic
versioning*](https://semver.org/). Semantic versioning is simply a set of
guidelines on how to manage your version number:
- The _major_ release number should be incremented whenever you introduce any
- The *major* release number should be incremented whenever you introduce any
backwards-incompatible changes. In other words, if you change your code
such that some other code which uses your code would break, you should
increment the major release number.
- The _minor_ release number should be incremented whenever you add any new
- The *minor* release number should be incremented whenever you add any new
(backwards-compatible) features to your project.
- The _patch_ release number should be incremented for backwards-compatible
- The *patch* release number should be incremented for backwards-compatible
bug-fixes and other minor changes.
If you like to automate things,
[`bumpversion`](https://github.com/peritus/bumpversion) is a simple tool that
you can use to help manage your version number.
<a class="anchor" id="include-the-version-in-your-code"></a>
### Include the version in your code
While the version of a library is ultimately defined in `setup.py`, it is
standard practice for a Python library to contain a version string called
`__version__` in the `__init__.py` file of the top-level package. For example,
our `example_project/mypackage/__init__.py` file contains this line:
> __version__ = '0.1.0'
> ```
> __version__ = '0.1.0'
> ```
This makes a library's version number programmatically accessible and
queryable.
<a class="anchor" id="deprecate-dont-remove"></a>
### Deprecate, don't remove!
If you really want to change your API, but can't bring yourself to increment
your major release number, consider
[_deprecating_](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)
[*deprecating*](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)
the old API, and postponing its removal until you are ready for a major
release. This will allow you to change your API, but retain
backwards-compatilbiity with the old API until it can safely be removed at the
next major release.
You can use the built-in
[`warnings`](https://docs.python.org/3.5/library/exceptions.html#DeprecationWarning)
module to warn about uses of deprecated items. There are also some
[third-party libraries](https://github.com/briancurtin/deprecation) which make
it easy to mark a function, method or class as being deprecated.
<a class="anchor" id="appendix-cookiecutter"></a>
## Appendix: Cookiecutter
It is worth mentioning
[Cookiecutter](https://github.com/audreyr/cookiecutter), a little utility
program which you can use to generate a skeleton file/directory structure for
a new Python project.
You need to give it a template (there are many available templates, including
for projects in languages other than Python) - a couple of useful templates
are the [minimal Python package
template](https://github.com/kragniz/cookiecutter-pypackage-minimal), and the
[full Python package
template](https://github.com/audreyr/cookiecutter-pypackage) (although the
latter is probably overkill for most).
Here is how to create a skeleton project directory based off the minimal
Python packagetemplate:
> ```
> pip install cookiecutter
>
> # tell cookiecutter to create a directory
> # from the pypackage-minimal template
> cookiecutter https://github.com/kragniz/cookiecutter-pypackage-minimal.git
>
> # cookiecutter will then prompt you for
> # basic information (e.g. projectname,
> # author name/email), and then create a
> # new directory containing the project
> # skeleton.
> ```
......
talks/structuring/structuring.md → advanced_topics/09_structuring_projects.md
View file @ 288d6c90
......@@ -13,15 +13,15 @@ directory.
* [Recommended project structure](#recommended-project-structure)
* [The `mypackage/` directory](#the-mypackage-directory)
* [`README`](#readme)
* [`LICENSE`](#license)
* [`requirements.txt`](#requirements-txt)
* [`setup.py`](#setup-py)
* [The `mypackage/` directory](#the-mypackage-directory)
* [`README`](#readme)
* [`LICENSE`](#license)
* [`requirements.txt`](#requirements-txt)
* [`setup.py`](#setup-py)
* [Appendix: Tests](#appendix-tests)
* [Appendix: Versioning](#appendix-versioning)
* [Include the version in your code](#include-the-version-in-your-code)
* [Deprecate, don't remove!](#deprecate-dont-remove)
* [Include the version in your code](#include-the-version-in-your-code)
* [Deprecate, don't remove!](#deprecate-dont-remove)
* [Appendix: Cookiecutter](#appendix-cookiecutter)
......@@ -59,7 +59,7 @@ look through it if you like.
The first thing you should do is make sure that all of your python code is
organised into a sensibly-named
[_package_](https://docs.python.org/3.5/tutorial/modules.html#packages). This
[*package*](https://docs.python.org/3/tutorial/modules.html#packages). This
is important, because it greatly reduces the possibility of naming collisions
when people install your library alongside other libraries. Hands up those of
you who have ever written a file called `utils.[py|m|c|cpp]`!
......@@ -100,10 +100,12 @@ standardised syntax. You can specify the exact version, or range of versions,
that your project requires. For example:
> six==1.*
> numpy==1.*
> scipy>=0.18,<2
> nibabel==2.*
> ```
> six==1.*
> numpy==1.*
> scipy>=0.18
> nibabel==2.*
> ```
If your project has optional dependencies, i.e. libraries which are not
......@@ -116,7 +118,9 @@ Having all your dependencies listed in a file in this way makes it easy for
others to install the dependencies needed by your project, simply by running:
> pip install -r requirements.txt
> ```
> pip install -r requirements.txt
> ```
<a class="anchor" id="setup-py"></a>
......@@ -168,7 +172,7 @@ The `setup.py` for our example project might look like this:
>
> name='Example project',
> description='Example Python project for PyTreat',
> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals/',
> url='https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020/',
> author='Paul McCarthy',
> author_email='pauldmccarthy@gmail.com',
> license='Apache License Version 2.0',
......@@ -214,7 +218,7 @@ There are no strict rules for where to put your tests (you have tests,
right?). There are two main conventions:
You can store your test files _inside_ your package directory:
You can store your test files *inside* your package directory:
> ```
......@@ -228,8 +232,7 @@ You can store your test files _inside_ your package directory:
> ```
Or, you can store your test files _alongside_ your package directory:
Or, you can store your test files *alongside* your package directory:
> ```
......@@ -261,7 +264,7 @@ really up to you.
If you are intending to make your project available for public use (e.g. on
[PyPI](https://pypi.python.org/pypi) and/or
[conda](https://anaconda.org/anaconda/repo)), it is __very important__ to
[conda](https://anaconda.org/anaconda/repo)), it is **very important** to
manage the version number of your project. If somebody decides to build their
software on top of your project, they are not going to be very happy with you
if you make substantial, API-breaking changes without changing your version
......@@ -271,11 +274,13 @@ number in an appropriate manner.
Python has [official standards](https://www.python.org/dev/peps/pep-0440/) on
what constitutes a valid version number. These standards can be quite
complicated but, in the vast majority of cases, a simple three-number
versioning scheme comprising _major_, _minor_, and _patch_ release
versioning scheme comprising *major*, *minor*, and *patch* release
numbers should suffice. Such a version number has the form:
> major.minor.patch
> ```
> major.minor.patch
> ```
For example, a version number of `1.3.2` has a _major_ release of 1, _minor_
......@@ -285,25 +290,25 @@ release of 3, and a _patch_ release of 2.
If you follow some simple and rational guidelines for versioning
`your_project`, then people who use your project can, for instance, specify
that they depend on `your_project==1.*`, and be sure that their code will work
for _any_ version of `your_project` with a major release of 1. Following these
for *any* version of `your_project` with a major release of 1. Following these
simple guidelines greatly improves software interoperability, and makes
everybody (i.e. developers of other projects, and end users) much happier!
Many modern Python projects use some form of [_semantic
versioning_](https://semver.org/). Semantic versioning is simply a set of
Many modern Python projects use some form of [*semantic
versioning*](https://semver.org/). Semantic versioning is simply a set of
guidelines on how to manage your version number:
- The _major_ release number should be incremented whenever you introduce any
- The *major* release number should be incremented whenever you introduce any
backwards-incompatible changes. In other words, if you change your code
such that some other code which uses your code would break, you should
increment the major release number.
- The _minor_ release number should be incremented whenever you add any new
- The *minor* release number should be incremented whenever you add any new
(backwards-compatible) features to your project.
- The _patch_ release number should be incremented for backwards-compatible
- The *patch* release number should be incremented for backwards-compatible
bug-fixes and other minor changes.
......@@ -322,7 +327,9 @@ standard practice for a Python library to contain a version string called
our `example_project/mypackage/__init__.py` file contains this line:
> __version__ = '0.1.0'
> ```
> __version__ = '0.1.0'
> ```
This makes a library's version number programmatically accessible and
......@@ -335,7 +342,7 @@ queryable.
If you really want to change your API, but can't bring yourself to increment
your major release number, consider
[_deprecating_](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)
[*deprecating*](https://en.wikipedia.org/wiki/Deprecation#Software_deprecation)
the old API, and postponing its removal until you are ready for a major
release. This will allow you to change your API, but retain
backwards-compatilbiity with the old API until it can safely be removed at the
......
talks/structuring/example_project/LICENSE → advanced_topics/09_structuring_projects/example_project/LICENSE
View file @ 288d6c90
The example_project library
Copyright 2016-2017 University of Oxford, Oxford, UK.
Copyright 2016-2020 University of Oxford, Oxford, UK.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
......
talks/structuring/example_project/setup.py → advanced_topics/09_structuring_projects/example_project/setup.py
View file @ 288d6c90
......@@ -21,7 +21,7 @@ setup(
name='Example project',
description='Example Python project for PyTreat',
url='https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals/',
url='https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020/',
author='Paul McCarthy',
author_email='pauldmccarthy@gmail.com',
license='Apache License Version 2.0',
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment