Fix files packaged in the release tarball.

We were still on .txt (not .rst) documentation files.

MANIFEST.in

@@ -1,4 +1,4 @@
-include README.txt COPYING setup.py MANIFEST.in
+include README.rst COPYING setup.py MANIFEST.in
 recursive-include rope *.py
-recursive-include docs *.txt
+recursive-include docs *.rst
 recursive-include ropetest *.py

docs/contributing.rst

@@ -34,13 +34,13 @@ googlegroups.com`_ mailing list.  Here is only a list of suggestions.
 Issues
 ------
 
-The `dev/issues.txt`_ file is actually the main rope todo file.  There
+The `dev/issues.rst`_ file is actually the main rope todo file.  There
 is a section called "unresolved issues"; it contains almost every kind
 of task.  Most of them need some thought or discussion.  Pickup
 whichever you are most interested in.  If you have ideas or questions
 about them, don't hesitate to discuss it in the mailing list.
 
-.. _`dev/issues.txt`: dev/issues.html
+.. _`dev/issues.rst`: dev/issues.rst
 
 Getting Ready For Python 3.0
 ----------------------------
@@ -54,10 +54,10 @@ Write Plugins For Other IDEs
 See ropemacs_, ropevim_, eric4_ and ropeide_.
 
 
-.. _ropemacs: http://rope.sf.net/ropemacs.html
-.. _ropevim: http://rope.sf.net/ropevim.html
-.. _ropeide: http://rope.sf.net/ropeide.html
-.. _eric4: http://www.die-offenbachs.de/eric/index.html
+.. _ropemacs: http://rope.sf.net/ropemacs.rst
+.. _ropevim: http://rope.sf.net/ropevim.rst
+.. _ropeide: http://rope.sf.net/ropeide.rst
+.. _eric4: http://www.die-offenbachs.de/eric/index.rst
 
 
 Rope Structure
@@ -69,10 +69,10 @@ Rope package structure:
 * `rope.refactor`: refactorings and tools used in them
 * `rope.contrib`: IDE helpers
 
-Have a look at ``__init__.py`` of these packages or `library.txt`_ for
+Have a look at ``__init__.py`` of these packages or `library.rst`_ for
 more information.
 
-.. _`library.txt`: library.html
+.. _`library.rst`: library.rst
 
 
 Source Repository

docs/dev/todo.rst

@@ -2,7 +2,7 @@
  TODO
 ======
 
-See the `unresolved issues` section of ``issues.txt`` file for more.
+See the `unresolved issues` section of ``issues.rst`` file for more.
 
 
 > Public Release 1.0

docs/library.rst

@@ -3,7 +3,7 @@
 =========================
 
 If you need other features, send a feature request.  Have a look at
-`contributing.txt`_.
+`contributing.rst`_.
 
 
 .. contents:: Table of Contents
@@ -235,9 +235,9 @@ that points to that folder.
 
 You can use this method for getting a resource (that is file or
 folder) inside a project.  Uses ``'/'``s for separating directories.
-For instance ``project.get_resource('my_folder/my_file.txt')`` returns
+For instance ``project.get_resource('my_folder/my_file.rst')`` returns
 a `rope.base.resources.File` object that points to
-``${projectroot}/my_folder/my_file.txt`` file.
+``${projectroot}/my_folder/my_file.rst`` file.
 
 Note that this method assumes the resource exists.  If it does not
 exist you can use `Project.get_file()` and `Project.get_folder()`
@@ -524,7 +524,7 @@ Restructuring
 -------------
 
 The example for replacing occurrences of our `pow` function to ``**``
-operator (see the restructuring section of `overview.txt`_)::
+operator (see the restructuring section of `overview.rst`_)::
 
   # Setting up the project
   >>> from rope.base.project import Project
@@ -557,8 +557,8 @@ operator (see the restructuring section of `overview.txt`_)::
 
 See code documentation and test suites for more information.
 
-.. _overview.txt: overview.html
-.. _contributing.txt: contributing.html
+.. _overview.rst: overview.rst
+.. _contributing.rst: contributing.rst
 
 
 Other Topics

docs/overview.rst

@@ -10,10 +10,10 @@ want to feel the power of rope try its features and see its unit
 tests.
 
 This file is more suitable for the users.  Developers who plan to use
-rope as a library might find library.txt_ more useful.
+rope as a library might find library.rst_ more useful.
 
 .. contents:: Table of Contents
-.. _library.txt: library.html
+.. _library.rst: library.rst
 
 
 ``.ropeproject`` Folder
@@ -746,7 +746,7 @@ will match (for instance, if ``exact`` is specified , ``${name}``
 matches ``name`` and ``x.name`` but not ``var`` nor ``(1 + 2)`` while
 a normal ``${name}`` can match all of them).
 
-For performing this refactoring using rope library see `library.txt`_.
+For performing this refactoring using rope library see `library.rst`_.
 
 
 Example 2
@@ -1108,7 +1108,7 @@ there is no version control at all.  Also don't forget to commit your
 changes yourself, rope doesn't do that.
 
 Adding support for other VCSs is easy; have a look at
-`library.txt`_.
+`library.rst`_.
 
 .. _pysvn: http://pysvn.tigris.org
 .. _Mercurial: http://selenic.com/mercurial

docs/rope.rst

@@ -45,10 +45,10 @@ Features implemented so far:
   * Handling built-in container types
   * Saving object information on disk and validating them
 
-For more information see `overview.txt`_.
+For more information see `overview.rst`_.
 
 
-.. _overview.txt: overview.html
+.. _overview.rst: overview.rst
 .. _pysvn: http://pysvn.tigris.org
 .. _Mercurial: http://selenic.com/mercurial
 .. _GIT: http://git.or.cz

rope/__init__.py

@@ -1,7 +1,7 @@
 """rope, a python refactoring library"""
 
 INFO = __doc__
-VERSION = '0.10.1'
+VERSION = '0.10.2'
 COPYRIGHT = """\
 Copyright (C) 2006-2012 Ali Gholami Rudi
 Copyright (C) 2009-2012 Anton Gritsay

rope/refactor/multiproject.py

@@ -1,6 +1,6 @@
 """This module can be used for performing cross-project refactorings
 
-See the "cross-project refactorings" section of ``docs/library.txt``
+See the "cross-project refactorings" section of ``docs/library.rst``
 file.
 
 """