<commit_before>==================
Installing Pyjamas
==================

BEFORE PROCEEDING READ THE FOLLOWING WARNING.

DO NOT install the pyjamas libraries into /usr/share/python-support,
/usr/lib/python2.N/site-packages or ANY location where the "standard"
python interpreter could possibly pick them up.  The pyjamas libraries
have nothing to do with python libraries when used by the compiler,
and contain replacements for sys.py, time.py and other modules that
are critical to pyjamas.   It goes without saying that if you overwrite
the standard python modules with the pyjamas equivalents, you will run into
massive problems.  Don't do it.

Dependencies
============

For pyjamas javascript compilation, you need python 2 - that's it.

For Pyjamas Desktop, you will need:

* python-jsonrpc which can be downloaded from http://json-rpc.org
  if you wish to use JSONRPC.

* Win32 comtypes; or python-hulahop and python-xpcom, or a patched
  version of pywebkitgtk and webkit-gobject

  These are for the MSHTML, XULrunner and Webkit ports of Pyjamas
  Desktop, respectively.

    Win32:

    * comtypes is available here: http://sourceforge.net/projects/comtypes/

    XULrunner:

    * python-xpcom requires XULrunner.  it's _big_.  it is recommended that
      you use a standard gnu/linux distribution build.  if you ever manage
      to get XULrunner and python-xpcom compiled for win32, you are officially
      a hero: please tell everyone about it on pyjamas-dev.

    Webkit:

    use this code, for now:
    * http://github.com/lkcl/webkit/16401.master
    * http://code.google.com/p/pywebkitgtk/issues/detail?id=13

Developer Sandbox Setup
=======================

In this directory run:

 python bootstrap.py

The files ``pyjd/__init__.py``, ``./bin/pyjsbuild`` and ``./bin/pyjscompile``
will be created, custom-tailored with hard-coded paths specific to the exact
absolute location that the bootstrap.py command is run from.  In this way, you
will be able to install, test and use multiple versions of Pyjamas, without
cross-interference.

As they contain hard-coded paths, these custom-tailored commands CANNOT
be "moved around".  If you move the pyjamas installation, re-run bootstrap.py
to recreate the commands, with suitable hard-coded paths.

To build pyjamas apps see ``./bin/pyjsbuild --help``


System Installation
===================

If you are installing pyjamas system-wide, for use by MORE THAN ONE
developer of the same multi-user system, run the following command.
Otherwise DO NOT run setup.py, see bootstrap.py.  If you are using Windows,
you are out of luck and should entirely avoid using setup.py.

First, you must use bootstrap.py to create suitable ./bin/pyjsbuild
and ./bin/pyjscompile commands.  For example:

 python boostrap.py /usr/bin /usr/share/pyjamas

After ./pyjd/__init__.py, ./bin/pyjsbuild and ./bin/pyjscompile have been
created, they can now be installed system-wide, along with the libraries.

 python run_bootstrap_first_then_setup.py install

You *may* need to specify --install-data={pickasuitablelocation}
and you *may* need to specify the same location to the bootstrap.py
command (prior to running run_bootstrap_first_then_setup.py)

 python bootstrap.py /usr/bin {pickasuitablelocation}

The commands pyjscompile and pyjsbuild will be installed;
the boilerplate web templates, the pyjamas "builtin" libraries
and the UI Widget libraries will be installed as data libraries
which pyjscompile and pyjsbuild will know about.   The default
path is:

    {sys.prefix}/share/pyjamas

You can over-ride this default location with the PYJSPREFIX
environment variable.

<commit_msg>spelling mistake spotted by <NAME> (thank you!)<commit_after>==================
Installing Pyjamas
==================

BEFORE PROCEEDING READ THE FOLLOWING WARNING.

DO NOT install the pyjamas libraries into /usr/share/python-support,
/usr/lib/python2.N/site-packages or ANY location where the "standard"
python interpreter could possibly pick them up.  The pyjamas libraries
have nothing to do with python libraries when used by the compiler,
and contain replacements for sys.py, time.py and other modules that
are critical to pyjamas.   It goes without saying that if you overwrite
the standard python modules with the pyjamas equivalents, you will run into
massive problems.  Don't do it.

Dependencies
============

For pyjamas javascript compilation, you need python 2 - that's it.

For Pyjamas Desktop, you will need:

* python-jsonrpc which can be downloaded from http://json-rpc.org
  if you wish to use JSONRPC.

* Win32 comtypes; or python-hulahop and python-xpcom, or a patched
  version of pywebkitgtk and webkit-gobject

  These are for the MSHTML, XULrunner and Webkit ports of Pyjamas
  Desktop, respectively.

    Win32:

    * comtypes is available here: http://sourceforge.net/projects/comtypes/

    XULrunner:

    * python-xpcom requires XULrunner.  it's _big_.  it is recommended that
      you use a standard gnu/linux distribution build.  if you ever manage
      to get XULrunner and python-xpcom compiled for win32, you are officially
      a hero: please tell everyone about it on pyjamas-dev.

    Webkit:

    use this code, for now:
    * http://github.com/lkcl/webkit/16401.master
    * http://code.google.com/p/pywebkitgtk/issues/detail?id=13

Developer Sandbox Setup
=======================

In this directory run:

 python bootstrap.py

The files ``pyjd/__init__.py``, ``./bin/pyjsbuild`` and ``./bin/pyjscompile``
will be created, custom-tailored with hard-coded paths specific to the exact
absolute location that the bootstrap.py command is run from.  In this way, you
will be able to install, test and use multiple versions of Pyjamas, without
cross-interference.

As they contain hard-coded paths, these custom-tailored commands CANNOT
be "moved around".  If you move the pyjamas installation, re-run bootstrap.py
to recreate the commands, with suitable hard-coded paths.

To build pyjamas apps see ``./bin/pyjsbuild --help``


System Installation
===================

If you are installing pyjamas system-wide, for use by MORE THAN ONE
developer of the same multi-user system, run the following command.
Otherwise DO NOT run setup.py, see bootstrap.py.  If you are using Windows,
you are out of luck and should entirely avoid using setup.py.

First, you must use bootstrap.py to create suitable ./bin/pyjsbuild
and ./bin/pyjscompile commands.  For example:

 python bootstrap.py /usr/bin /usr/share/pyjamas

After ./pyjd/__init__.py, ./bin/pyjsbuild and ./bin/pyjscompile have been
created, they can now be installed system-wide, along with the libraries.

 python run_bootstrap_first_then_setup.py install

You *may* need to specify --install-data={pickasuitablelocation}
and you *may* need to specify the same location to the bootstrap.py
command (prior to running run_bootstrap_first_then_setup.py)

 python bootstrap.py /usr/bin {pickasuitablelocation}

The commands pyjscompile and pyjsbuild will be installed;
the boilerplate web templates, the pyjamas "builtin" libraries
and the UI Widget libraries will be installed as data libraries
which pyjscompile and pyjsbuild will know about.   The default
path is:

    {sys.prefix}/share/pyjamas

You can over-ride this default location with the PYJSPREFIX
environment variable.


{'fraction_non_alphanumeric': 0.08747433264887064, 'fraction_numerical': 0.004106776180698152, 'mean_word_length': 4.155963302752293, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2580745', 'n_tokens_mistral': 2147, 'n_tokens_neox': 2007, 'n_words': 904}