Changes between Version 4 and Version 5 of FAQ


Ignore:
Timestamp:
06/29/2012 10:55:49 PM (12 months ago)
Author:
rmtew
Comment:

Converted page to trac markup just to get the PageOutline? to work.

Legend:

Unmodified
Added
Removed
Modified

  • FAQ

    v4 v5  
    1 {{{ 
    2 #!rst 
     1[[PageOutline(1,Frequently Asked Questions)]] 
    32 
    4 === 
    5 FAQ 
    6 === 
    7  
    8 How compatible is using Stackless instead of regular Python? 
    9 ============================================================ 
     3= Is this compatible with regular Python? = 
    104 
    115It is possible to use Stackless in place of regular Python. 
    … …  
    148previously compiled against regular Python. 
    159 
    16 **There are some exceptions however..**: 
     10**There are some exceptions however..** 
    1711 
    18   - Not all extensions are implemented in a friendly manner, 
    19     and because of this may be unstable or unusable when combined 
    20     with Stackless Python. One example of this, is PyQT_, which 
    21     is based on an unfriendly package named SIP_. Read 
    22     `this thread <http://www.stackless.com/pipermail/stackless/2007-April/000142.html>`_ 
    23     for further information. 
     12* Not all extensions are implemented in a friendly manner, 
     13  and because of this may be unstable or unusable when combined 
     14  with Stackless Python. One example of this, is [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQT], which 
     15  is based on an unfriendly package named [http://www.riverbankcomputing.co.uk/software/sip/intro SIP]. Read 
     16  [http://www.stackless.com/pipermail/stackless/2007-April/000142.html this thread] 
     17  for further information. 
    2418 
    25   - The greenlet_ extension module was extracted from Stackless 
    26     Python, and provides a portion of the functionality that 
    27     Stackless does. Because of this, using it with Stackless 
    28     is an odd choice, and will not be supported in any way 
    29     by the Stackless developers. 
     19* The [http://pypi.python.org/pypi/greenlet greenlet] extension module was extracted from Stackless 
     20  Python, and provides a portion of the functionality that 
     21  Stackless does. Because of this, using it with Stackless 
     22  is an odd choice, and will not be supported in any way 
     23  by the Stackless developers. 
    3024 
    3125 
    32 What's involved in installing Stackless alongside regular Python? 
    33 ================================================================= 
     26= What's involved in installing Stackless alongside regular Python? = 
    3427 
    35 For Windows 
    36 ----------- 
     28== For Windows == 
    3729 
    3830It depends on whether you are using the installers or not. 
    … …  
    4739Stackless Python, in order to behave compatibly, needs to use the 
    4840same DLL names. If an installation of regular Python 2.6 has its 
    49 ``python26.dll`` in place, then there is no way for Stackless to 
    50 have its ``python26.dll`` as a file of exactly the same name. 
     41''python26.dll'' in place, then there is no way for Stackless to 
     42have its ''python26.dll'' as a file of exactly the same name. 
    5143 
    5244Otherwise you always have the option of having regular Python of 
    … …  
    5547invoke it there when you have a need to do so. 
    5648 
    57 For Unix-like systems 
    58 --------------------- 
     49== For Unix-like systems == 
    5950 
    6051It depends on the unique and special ways in which your particular 
    … …  
    6253 
    6354By default, when you compile and install Stackless, it will install 
    64 into ``/usr/local`` with its executable also named python. Your 
     55into ''/usr/local'' with its executable also named python. Your 
    6556distribution provided regular Python installation, is most likely 
    66 installed in ``/usr``, and the Stackless Python executable will 
     57installed in ''/usr'', and the Stackless Python executable will 
    6758override its existing executable. The recommended approach is to 
    68 rename the Stackless Python executable to ``spython``, so that you 
     59rename the Stackless Python executable to ''spython'', so that you 
    6960can explicitly run it, but still have regular Python available as 
    7061python as it was before you installed Stackless. 
    7162 
    72 There are two wikis.. WTF? 
    73 ========================== 
     63= There are two wikis? = 
    7464 
    7565Yes, there are. This is because of historical reasons. For now 
    7666example code intended for direct use and examination by user 
    7767should go into the examples Subversion repository and described in 
    78 `its wiki <http://code.google.com/p/stacklessexamples/wiki/StacklessExamples>`_. 
     68[http://code.google.com/p/stacklessexamples/wiki/StacklessExamples its wiki]. 
    7969 
    8070This wiki better suits having example code and snippets for the 
    8171purposes illustrating the documentation which is provided here . 
    8272 
    83 Where do i find more tutorials and resources? 
    84 ============================================= 
     73= Where do i find more tutorials and resources? = 
    8574 
    86 You can visit `this page <http://islab.org/stackless/>`_ for more 
     75You can visit [http://islab.org/stackless/ this page] for more 
    8776tutorials and resources on stackless python. 
    88  
    89 .. _PYQT : http://www.riverbankcomputing.co.uk/software/pyqt/intro 
    90 .. _SIP : http://www.riverbankcomputing.co.uk/software/sip/intro 
    91 .. _greenlet : http://pypi.python.org/pypi/greenlet 
    92 }}}