[py-svn] r10846 - py/dist/py/documentation
hpk at codespeak.net
hpk at codespeak.net
Tue Apr 19 13:27:59 CEST 2005
Author: hpk
Date: Tue Apr 19 13:27:59 2005
New Revision: 10846
Modified:
py/dist/py/documentation/getting_started.txt
py/dist/py/documentation/releasescheme.txt
Log:
adjustments, recommended way is now to
'svn co' things to py-dist instead of dist-py.
This allows command line completion to remain
sensible.
Modified: py/dist/py/documentation/getting_started.txt
==============================================================================
--- py/dist/py/documentation/getting_started.txt (original)
+++ py/dist/py/documentation/getting_started.txt Tue Apr 19 13:27:59 2005
@@ -21,10 +21,10 @@
Checkout the py lib distribution tree with subversion, e.g. use::
- svn co http://codespeak.net/svn/py/dist dist-py
+ svn co http://codespeak.net/svn/py/dist py-dist
to checkout the code, documentation, tool and example tree
-into a ``dist-py`` checkout directory. Your naming desire may vary
+into a ``py-dist`` checkout directory. Your naming desire may vary
for your local checkout directory.
If you experience problems with the subversion checkout e.g.
@@ -37,13 +37,13 @@
-------------
You need to put the checkout-directory into your ``PYTHONPATH``
-and you want to have the ``dist-py/py/bin/py.test`` script in
+and you want to have the ``py-dist/py/bin/py.test`` script in
your system path, which lets you execute test files and directories.
There already is a convenient way for Bash/Shell based systems
to setup the ``PYTHONPATH`` as well as the shell ``PATH``, insert::
- eval `python ~/path/to/dist-py/py/env.py`
+ eval `python ~/path/to/py-dist/py/env.py`
into your ``.bash_profile``. Of course, you need to
specify your own checkout-directory.
Modified: py/dist/py/documentation/releasescheme.txt
==============================================================================
--- py/dist/py/documentation/releasescheme.txt (original)
+++ py/dist/py/documentation/releasescheme.txt Tue Apr 19 13:27:59 2005
@@ -1,9 +1,9 @@
The directory release layout of the repository::
- svn/py/dist # latest released code
- svn/py/tag/py-X.Y.Z # tagged releases
- svn/py/branch/py-X.Y # contains release branch development
- svn/py/trunk # head development
+ svn/py/dist # latest released code
+ svn/py/tag/py-X.Y.Z # tagged releases
+ svn/py/branch/py-X.Y # contains release branch development
+ svn/py/trunk # head development
Scenario "no svn and just let me play, please"
==============================================
More information about the pytest-commit
mailing list