[pygr-notify] [pygr] r270 committed - Edited wiki page through web user interface.

[codesite-noreply at google.com]

Revision: 270
Author: marecki
Date: Sat Sep 19 01:29:22 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/pygr/source/detail?r=270

Modified:
  /wiki/BuildingAndTestingPygr.wiki

=======================================
--- /wiki/BuildingAndTestingPygr.wiki	Mon Jul 27 17:36:08 2009
+++ /wiki/BuildingAndTestingPygr.wiki	Sat Sep 19 01:29:22 2009
@@ -78,7 +78,7 @@

  === Building and Installing Pygr ===

-If you want your Pygr installation to be system-wide, the procedure is  
exactly the same as for Pyrex - obtain the sources, enter the directory and  
run _python setup.py install_ (possibly with _-O_). If however your  
installation is only to be local, you've got two options:
+If you want your Pygr installation to be system-wide, the procedure is  
exactly the same as for Pyrex - obtain the sources, enter the directory and  
run _python setup.py install_ (possibly with _-Ox_). If however your  
installation is only to be local, you've got two options:

   * run _python setup.py build_. This will prepare a local directory  
containing a clean and complete build of Pygr but stop short of copying its  
contents to a system-wide location; you can then copy these contents by  
hand to wherever you want them to be and as long as you specify this  
directory in _sys.path_, Python will be able to find Pygr - and other  
modules which may be installed in it - there. You will find this build in  
the system-dependent directory *build/lib._OS_-_ARCH_-_PV_*, _e.g._  
_build/lib.linux-x86_64-2.5_. After you're done, the Pygr sources can  
safely be deleted;

@@ -94,10 +94,15 @@
  Running the tests will display some information pertaining to their  
progress, followed by a summary. If everything is right, all tests should  
pass. Depending of what optional components are present in your system you  
may observe some test suites having been skipped.


+=== Packaging ===
+
+Instead of installing Pygr into the local Python package tree using  
_install_ one may opt to create an appropriate *package* and either install  
the package instead (e.g. to have Pygr under the control of a package  
manager) or share it with users who for either can't or don't want to build  
Pygr from source. A wide selection of binary packages of Pygr can be found  
on our Downloads page; to find out how to create packages of different  
formats or to learn more about how we build the provided ones, see the  
PackagingPygr Wiki page.
+
+
  == Known Issues ==

-The setup script fails to invoke Pyrex correctly under Python 2.3 if  
setuptools are installed. Specifically, the following condition must be met  
for this bug to trigger:
- * building Pygr for Python 2.3;
+The setup script fails to invoke Pyrex correctly under Python 2.3/2.4 if  
setuptools are installed. Specifically, the following condition must be met  
for this bug to trigger:
+ * building Pygr for Python 2.3/2.4;
   * setuptools are installed and get imported correctly;
   * Pyrex-generated .c files are not present _or_ are older than  
respective .pyx files.
  This appears to be a bug in setuptools; we have confirmed it to be present  
in version 0.6c9 of the package. Note that this problem should not affect  
users installing packaged releases of Pygr, as these are shipped with  
pre-built .c files and thus do not invoke Pyrex.