[pygr-notify] [pygr commit] r214 - Edited wiki page through web user interface.

[codesite-noreply at google.com]

Author: marecki
Date: Wed May  6 17:33:27 2009
New Revision: 214

Modified:
    wiki/BuildingAndTestingPygr.wiki

Log:
Edited wiki page through web user interface.

Modified: wiki/BuildingAndTestingPygr.wiki
==============================================================================
--- wiki/BuildingAndTestingPygr.wiki	(original)
+++ wiki/BuildingAndTestingPygr.wiki	Wed May  6 17:33:27 2009
@@ -39,19 +39,31 @@
  Pygr should work correctly with any version of Python between 2.3 and 2.6,  
inclusive. Python 3.0 is *not* supported and no conversion has been planned  
yet, primarily because even its latest version (3.0.1) exhibits  
[http://mail.python.org/pipermail/python-dev/2009-January/085590.html  
visibly worse I/O performance] than the 2.x branch.


+=== Installing Pyrex ===
+
+Pygr extension code is written in  
[http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/ Pyrex] rather  
than plain C, thus making it necessary for Pyrex to be present at build  
time.
+
+Pyrex hasn't been officially declared finished yet, which means two things  
to Pygr users: one is that you'll want the latest available version (as of  
now, 0.9.8.5) in order to avoid bugs, the other is that you'll need to  
build the module by hand. Fortunately the latter is very easy:
+ * download and unpack the archive;
+ * launch a command-line interpreter and enter the newly-created directory;
+ * run _python setup.py install_, possibly adding the option _-O_ if you  
want optimised files to be installed too. You may need to be more specific  
than saying just _python_ if multiple versions are present and/or the main  
executable is not in the path.
+
+In case of Pygr Pyrex is only required at build time, it can safely be  
removed afterwards.
+
+
  === The C Compiler etc. ===

-Pygr is not a pure-Python module and a C compiler must be present at build  
time for it to finish successfully. You will also need Python's header  
files. How all these should be obtained depends a lot on the system you use:
+Pygr is not a pure-Python module and a C compiler, along with possible  
assistant tools, must be present at build time for it to finish  
successfully. You will also need Python's header files. How all these  
should be obtained depends a lot on the system you use:
+
   * if you built Python from source, you should already have everything;
+
   * if under Linux/Unix/Fink/Cygwin/..., Python's header files may be  
distributed separately from its executables and other run-time files. Look  
for something similar to _python-devel_ in your package manager; installing  
it should automatically pull in all dependencies. As for the compiler, you  
will most likely use GCC - almost certainly available in your system's  
package repositories, if not already on your hard drive;
+
   * under Windows, your Python installation should come with all the  
required header files but things are more complicated when it comes to the  
compiler. There are two options available here, they will be discussed in  
more details later:
    * use Microsoft Visual Studio and the official Microsoft Platform SDK; or
    * use MinGW, port of GCC and friends to Windows bundled with  
freely-distributable standard header files and import libraries.

-
-=== Installing Pyrex ===
-
-At the time of writing these notes Pyrex is
+Like Pyrex, both the compiler and the header files are build-time  
dependencies only. They can safely be removed afterwards.


  == Building under Windows ==