package.ps1 now fetches all dependencies

Don't literally check in Python since it looks dodgy (rightfully so).
Instead the build script just fetches it.

* Update README, simplifying language and documenting other projects

1 files changed, 0 insertions, 27 deletions

diff --git a/FOSS/Python/Dependencies/future-0.18.2/docs/conversion_limitations.rst b/FOSS/Python/Dependencies/future-0.18.2/docs/conversion_limitations.rst
deleted file mode 100644
index c2b1530..0000000
--- a/FOSS/Python/Dependencies/future-0.18.2/docs/conversion_limitations.rst
+++ /dev/null
@@ -1,27 +0,0 @@
-.. _futurize-limitations:
-
-Known limitations
------------------
-
-``futurize`` and ``pasteurize`` are useful to automate much of the
-work of porting, particularly the boring repetitive text substitutions. They also
-help to flag which parts of the code require attention.
-
-Nevertheless, ``futurize`` and ``pasteurize`` are still incomplete and make
-some mistakes, like 2to3, on which they are based. Please report bugs on
-`GitHub <https://github.com/PythonCharmers/python-future/>`_. Contributions to
-the ``lib2to3``-based fixers for ``futurize`` and ``pasteurize`` are
-particularly welcome! Please see :ref:`contributing`.
-
-``futurize`` doesn't currently make the following change automatically:
-
-1. Strings containing ``\U`` produce a ``SyntaxError`` on Python 3. An example is::
-
-       s = 'C:\Users'.
-
-   Python 2 expands this to ``s = 'C:\\Users'``, but Python 3 requires a raw
-   prefix (``r'...'``). This also applies to multi-line strings (including
-   multi-line docstrings).
-
-Also see the tests in ``future/tests/test_futurize.py`` marked
-``@expectedFailure`` or ``@skip`` for known limitations.