mirror of
https://github.com/roytam1/palemoon27.git
synced 2026-05-26 14:30:27 +00:00
roytam1
98894236c9
- Bug 1171200 - Add means of checking if a document links to a manifest. r=billm (066ddad20) - Bug 1167300 - Consolidate the performance tool directory, r=jsantell (c7dd7dc34) - Bug 1167300 - Create a way to get strings from multiple localization files, r=jsantell (0973b8d3e) - modules not in gre (914e4080e) - Bug 1153011 - Remove zoom button from call tree. r=vporof (797b8f91d) - Bug 1151973 - Inverted call tree should be ordered by 'self cost', not 'total cost', r=jsantell (f2800b272) - more gre removal (27aed87a0) - Bug 1144034 - Flamegraph text is barely readable on non-retina display, r=jsantell (cb19fd9f2) - Bug 1151973 - Inverted call tree should be ordered by 'self cost', not 'total cost', r=jsantell (9c579599e) - Bug 1167300 - Fix all performance tool imports to work with the new file locations, r=jsantell (70b2995c4) - Bug 1167298 - Remove the ordinal property on categories, r=jsantell (00b3f5830) - Bug 1167733 - Consolidate prefs access and usage in the new performance tool, r=jsantell (4dab15e7f) - Bug 1167006 - part 3 fully revert merge from 780e1f999f54. (8aaa33c9c) - Bug 1167961 - Task is incorrectly used in compatibility.js, r=jsantell (7291f68d1) - Bug 1138641 - Updated remaining callsites to use newChannel2 in browser/devtools (r=vporof) (60ac4b2c8) - Bug 1164130 - Correctly include RecordingUtils when importing older version 2 profiler data. r=vp (8169d0398) - Bug 1167962 - Keep exports at bottom of modules, r=jsantell (7426919db) - Bug 1167962 - Fix import in synthesizeProfileForTest, r=orange (cc7fab771) - fix merge of later patch Bug 1167006 (c0b57b0e2) - Bug 1157523 - Fix intermittent where markers are selected in the waterfall views when there is no recording selected. r=vp (35cec0bd1) - Bug 1196253 - update in-tree psutil to 3.1.1. r=gps (80f243738)
117 lines
3.0 KiB
ReStructuredText
117 lines
3.0 KiB
ReStructuredText
============================
|
|
Installing using pip on UNIX
|
|
============================
|
|
|
|
The easiest way to install psutil on UNIX is by using pip (but first you might
|
|
need to install python header files; see later).
|
|
First install pip::
|
|
|
|
$ wget https://bootstrap.pypa.io/get-pip.py
|
|
$ python get-pip.py
|
|
|
|
...then run::
|
|
|
|
$ pip install psutil
|
|
|
|
You may need to install gcc and python header files first (see later).
|
|
|
|
|
|
=====================
|
|
Installing on Windows
|
|
=====================
|
|
|
|
Just get the right installer for your Python version and architecture from:
|
|
https://pypi.python.org/pypi/psutil/#downloads
|
|
Since wheels installers are also available you may also use pip.
|
|
|
|
|
|
========================================
|
|
Compiling on Windows using Visual Studio
|
|
========================================
|
|
|
|
In order to compile psutil on Windows you'll need Visual Studio (Mingw32 is
|
|
no longer supported). You must have the same version of Visual Studio used to compile
|
|
your installation of Python, that is::
|
|
|
|
* Python 2.6: VS 2008
|
|
* Python 2.7: VS 2008
|
|
* Python 3.3, 3.4: VS 2010 (you can download it from `MS website <http://www.visualstudio.com/downloads/download-visual-studio-vs#d-2010-express>`_)
|
|
* Python 3.5: `VS 2015 UP <http://www.visualstudio.com/en-au/news/vs2015-preview-vs>`_
|
|
|
|
...then run::
|
|
|
|
setup.py build
|
|
|
|
...or::
|
|
|
|
make.bat build
|
|
|
|
Compiling 64 bit versions of Python 2.6 and 2.7 with VS 2008 requires
|
|
Windows SDK and .NET Framework 3.5 SP1 to be installed first.
|
|
Once you have those run vcvars64.bat, then compile:
|
|
http://stackoverflow.com/questions/11072521/
|
|
|
|
===================
|
|
Installing on Linux
|
|
===================
|
|
|
|
gcc is required and so the python headers. They can easily be installed by
|
|
using the distro package manager. For example, on Debian and Ubuntu::
|
|
|
|
$ sudo apt-get install gcc python-dev
|
|
|
|
...on Redhat and CentOS::
|
|
|
|
$ sudo yum install gcc python-devel
|
|
|
|
Once done, you can build/install psutil with::
|
|
|
|
$ python setup.py install
|
|
|
|
|
|
==================
|
|
Installing on OS X
|
|
==================
|
|
|
|
OS X installation from source will require gcc which you can obtain as part of
|
|
the 'XcodeTools' installer from Apple. Then you can run the standard distutils
|
|
commands.
|
|
To build only::
|
|
|
|
$ python setup.py build
|
|
|
|
To install and build::
|
|
|
|
$ python setup.py install
|
|
|
|
|
|
=====================
|
|
Installing on FreeBSD
|
|
=====================
|
|
|
|
The same compiler used to install Python must be present on the system in order
|
|
to build modules using distutils. Assuming it is installed, you can build using
|
|
the standard distutils commands.
|
|
|
|
Build only::
|
|
|
|
$ python setup.py build
|
|
|
|
Install and build::
|
|
|
|
$ python setup.py install
|
|
|
|
|
|
========
|
|
Makefile
|
|
========
|
|
|
|
A makefile is available for both UNIX and Windows (make.bat). It provides
|
|
some automations for the tasks described above and might be preferred over
|
|
using setup.py. With it you can::
|
|
|
|
$ make install # just install (in --user mode)
|
|
$ make uninstall # uninstall (needs pip)
|
|
$ make test # run tests
|
|
$ make clean # remove installation files
|