Skip to content
Commits on Source (28)
The ChangeLog file is no longer used.
For a list of changes goto: https://gitlab.gnome.org/GNOME/nautilus-python/commits/master
Installation Instructions
*************************
Copyright (C) 1994-1996, 1999-2002, 2004-2016 Free Software
Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
Basic Installation
==================
Briefly, the shell command './configure && make && make install'
should configure, build, and install this package. The following
more-detailed instructions are generic; see the 'README' file for
instructions specific to this package. Some packages provide this
'INSTALL' file but do not implement all of the features documented
below. The lack of an optional feature in a given package is not
necessarily a bug. More recommendations for GNU packages can be found
in *note Makefile Conventions: (standards)Makefile Conventions.
The 'configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a 'Makefile' in each directory of the package.
It may also create one or more '.h' files containing system-dependent
definitions. Finally, it creates a shell script 'config.status' that
you can run in the future to recreate the current configuration, and a
file 'config.log' containing compiler output (useful mainly for
debugging 'configure').
It can also use an optional file (typically called 'config.cache' and
enabled with '--cache-file=config.cache' or simply '-C') that saves the
results of its tests to speed up reconfiguring. Caching is disabled by
default to prevent problems with accidental use of stale cache files.
If you need to do unusual things to compile the package, please try
to figure out how 'configure' could check whether to do them, and mail
diffs or instructions to the address given in the 'README' so they can
be considered for the next release. If you are using the cache, and at
some point 'config.cache' contains results you don't want to keep, you
may remove or edit it.
The file 'configure.ac' (or 'configure.in') is used to create
'configure' by a program called 'autoconf'. You need 'configure.ac' if
you want to change it or regenerate 'configure' using a newer version of
'autoconf'.
The simplest way to compile this package is:
1. 'cd' to the directory containing the package's source code and type
'./configure' to configure the package for your system.
Running 'configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type 'make' to compile the package.
3. Optionally, type 'make check' to run any self-tests that come with
the package, generally using the just-built uninstalled binaries.
4. Type 'make install' to install the programs and any data files and
documentation. When installing into a prefix owned by root, it is
recommended that the package be configured and built as a regular
user, and only the 'make install' phase executed with root
privileges.
5. Optionally, type 'make installcheck' to repeat any self-tests, but
this time using the binaries in their final installed location.
This target does not install anything. Running this target as a
regular user, particularly if the prior 'make install' required
root privileges, verifies that the installation completed
correctly.
6. You can remove the program binaries and object files from the
source code directory by typing 'make clean'. To also remove the
files that 'configure' created (so you can compile the package for
a different kind of computer), type 'make distclean'. There is
also a 'make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
7. Often, you can also type 'make uninstall' to remove the installed
files again. In practice, not all packages have tested that
uninstallation works correctly, even though it is required by the
GNU Coding Standards.
8. Some packages, particularly those that use Automake, provide 'make
distcheck', which can by used by developers to test that all other
targets like 'make install' and 'make uninstall' work correctly.
This target is generally not run by end users.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the 'configure' script does not know about. Run './configure --help'
for details on some of the pertinent environment variables.
You can give 'configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here is
an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU 'make'. 'cd' to the
directory where you want the object files and executables to go and run
the 'configure' script. 'configure' automatically checks for the source
code in the directory that 'configure' is in and in '..'. This is known
as a "VPATH" build.
With a non-GNU 'make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use 'make distclean' before
reconfiguring for another architecture.
On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple '-arch' options to the
compiler but only a single '-arch' option to the preprocessor. Like
this:
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CPP="gcc -E" CXXCPP="g++ -E"
This is not guaranteed to produce working output in all cases, you
may have to build one architecture at a time and combine the results
using the 'lipo' tool if you have problems.
Installation Names
==================
By default, 'make install' installs the package's commands under
'/usr/local/bin', include files under '/usr/local/include', etc. You
can specify an installation prefix other than '/usr/local' by giving
'configure' the option '--prefix=PREFIX', where PREFIX must be an
absolute file name.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like '--bindir=DIR' to specify different values for particular
kinds of files. Run 'configure --help' for a list of the directories
you can set and what kinds of files go in them. In general, the default
for these options is expressed in terms of '${prefix}', so that
specifying just '--prefix' will affect all of the other directory
specifications that were not explicitly provided.
The most portable way to affect installation locations is to pass the
correct locations to 'configure'; however, many packages provide one or
both of the following shortcuts of passing variable assignments to the
'make install' command line to change installation locations without
having to reconfigure or recompile.
The first method involves providing an override variable for each
affected directory. For example, 'make install
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
'${prefix}'. Any directories that were specified during 'configure',
but not in terms of '${prefix}', must each be overridden at install time
for the entire installation to be relocated. The approach of makefile
variable overrides for each directory variable is required by the GNU
Coding Standards, and ideally causes no recompilation. However, some
platforms have known limitations with the semantics of shared libraries
that end up requiring recompilation when using this method, particularly
noticeable in packages that use GNU Libtool.
The second method involves providing the 'DESTDIR' variable. For
example, 'make install DESTDIR=/alternate/directory' will prepend
'/alternate/directory' before all installation names. The approach of
'DESTDIR' overrides is not required by the GNU Coding Standards, and
does not work on platforms that have drive letters. On the other hand,
it does better at avoiding recompilation issues, and works well even
when some directory options were not specified in terms of '${prefix}'
at 'configure' time.
Optional Features
=================
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving 'configure' the
option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
Some packages pay attention to '--enable-FEATURE' options to
'configure', where FEATURE indicates an optional part of the package.
They may also pay attention to '--with-PACKAGE' options, where PACKAGE
is something like 'gnu-as' or 'x' (for the X Window System). The
'README' should mention any '--enable-' and '--with-' options that the
package recognizes.
For packages that use the X Window System, 'configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the 'configure' options '--x-includes=DIR' and
'--x-libraries=DIR' to specify their locations.
Some packages offer the ability to configure how verbose the
execution of 'make' will be. For these packages, running './configure
--enable-silent-rules' sets the default to minimal output, which can be
overridden with 'make V=1'; while running './configure
--disable-silent-rules' sets the default to verbose, which can be
overridden with 'make V=0'.
Particular systems
==================
On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
HP-UX 'make' updates targets which have the same time stamps as their
prerequisites, which makes it generally unusable when shipped generated
files such as 'configure' are involved. Use GNU 'make' instead.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
parse its '<wchar.h>' header file. The option '-nodtk' can be used as a
workaround. If GNU CC is not installed, it is therefore recommended to
try
./configure CC="cc"
and if that doesn't work, try
./configure CC="cc -nodtk"
On Solaris, don't put '/usr/ucb' early in your 'PATH'. This
directory contains several dysfunctional programs; working variants of
these programs are available in '/usr/bin'. So, if you need '/usr/ucb'
in your 'PATH', put it _after_ '/usr/bin'.
On Haiku, software installed for all users goes in '/boot/common',
not '/usr/local'. It is recommended to use the following options:
./configure --prefix=/boot/common
Specifying the System Type
==========================
There may be some features 'configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, 'configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
'--build=TYPE' option. TYPE can either be a short name for the system
type, such as 'sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS
KERNEL-OS
See the file 'config.sub' for the possible values of each field. If
'config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option '--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with '--host=TYPE'.
Sharing Defaults
================
If you want to set default values for 'configure' scripts to share,
you can create a site shell script called 'config.site' that gives
default values for variables like 'CC', 'cache_file', and 'prefix'.
'configure' looks for 'PREFIX/share/config.site' if it exists, then
'PREFIX/etc/config.site' if it exists. Or, you can set the
'CONFIG_SITE' environment variable to the location of the site script.
A warning: not all 'configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to 'configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the 'configure' command line, using 'VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified 'gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
Autoconf limitation. Until the limitation is lifted, you can use this
workaround:
CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
'configure' Invocation
======================
'configure' recognizes the following options to control how it
operates.
'--help'
'-h'
Print a summary of all of the options to 'configure', and exit.
'--help=short'
'--help=recursive'
Print a summary of the options unique to this package's
'configure', and exit. The 'short' variant lists options used only
in the top level, while the 'recursive' variant lists options also
present in any nested packages.
'--version'
'-V'
Print the version of Autoconf used to generate the 'configure'
script, and exit.
'--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally 'config.cache'. FILE defaults to '/dev/null' to
disable caching.
'--config-cache'
'-C'
Alias for '--cache-file=config.cache'.
'--quiet'
'--silent'
'-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to '/dev/null' (any error
messages will still be shown).
'--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
'configure' can determine that directory automatically.
'--prefix=DIR'
Use DIR as the installation prefix. *note Installation Names:: for
more details, including other options available for fine-tuning the
installation locations.
'--no-create'
'-n'
Run the configure checks, but stop before creating any output
files.
'configure' also accepts some other, not widely useful, options. Run
'configure --help' for more details.
Adam Plumb
E-mail: adamplumb@gmail.com
Userid: adamplumb
ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src examples
if ENABLE_GTK_DOC
SUBDIRS += docs
CLEANFILES = html.stamp
endif
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = nautilus-python.pc
EXTRA_DIST = nautilus-python.pc.in
DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc
This diff is collapsed.
1.2.3:
- First release from gitlab
- Fixed open-terminal example extension (Maximillian Schambach)
- Fixed invalid DOAP file category (Andre Klapper)
- Fixed bug #3, setting argv[0] to thunar
- Fixed bug #4, allow overriding the build date to enable reproducible builds
- Removed build warnings (Christian Stadelman)
- Fix to work with python 3.8 (stratakis)
1.2.2:
- Fixed bug #792427, Fix folder string comparison to prevent duplicate extension loading
1.2.1:
- Fixed bug #792348, Fix syntax error when building docs using python3
1.2:
- Added capability to compile with python 3 support using PYTHON environment variable
- Fix #781232, Improve extension path loading semantics to follow XDG recommendations
- Fix #791208, require Nautilus 3.0 before importing extensions to prevent warnings
- Switch to using gtkdoc mkhtml for generating devhelp2 documentation
1.1:
- Added pygobject3 compatibility. Retained pygobject 2.28.x compatibility.
Updated extension examples to support pygobject3.
- Fixed bug #660290. Updated the FSF address
- Fixed bug #660288. Fix autogen warnings with additional macro ACLOCAL_AMFLAGS
- Fixed bug #660287. Make the docdir not hard-coded
- Fixed bug #660286. Fixes m4 underquoting warning
- Fixed bug #660283. Fixes html docs installation issue
- Fixed bug #653169. Upated the COPYING file with the most recent GPLv2 license
1.0.0:
- Use the gobject instrospection dynamic bindings, breaks compatibility
for existing extensions.
- For Nautilus3, the get_toolbar_items methods have been removed. (Only reporting
that change, it isn't up to us). Should still work with Nautilus 2.x annotations.
- No longer look in the old ~/.nautilus/python-extensions or /usr/lib/nautilus/extensions2.0/python
folders for extensions. Now look in ~/.local/share/nautilus-python/extensions or
$XDG_DATA_DIR/nautilus-python/extensions. Extensions should be arch-independent now.
- General clean up of the repository, removed old .cvsignore files
- Updated the gtk-doc documentation and examples to work with new dynamic bindings.
0.7.3:
- Use PyCapsule_Import for pygobject as well as pygtk
- Fixed bug #644399, in the property page example plugin, get the md5sum
of the file contents, not the file name
- Removed extraneous .cvsignore files
- Fixed the update-file-info-async example plugin
0.7.2:
- Fix to get the PyCapsule patch to work even if there is no PyCapsule
object set up for pygtk.
0.7.1:
- Fixed AM_CHECK_PYTHON_LIBS usage of test (GNOME bug #619440)
- Cleaned up the docs Makefile.am to make it more consistent
- Fix some python3 syntax issues in the python.m4 script
- Add python 2.7 support (GNOME bug #633171)
0.7.0:
- Added methods:
nautilus.InfoProvider.update_file_info_full
nautilus.InfoProvider.update_complete_invoke
nautilus.InfoProvider.cancel_update
nautilus.MenuProvider.get_file_items_full
nautilus.MenuProvider.get_background_items_full
nautilus.MenuProvider.get_toolbar_items_full
nautilus.MenuProvider.emit_items_updated_signal
- Added complete gtk-doc documentation: tutorial and reference. Enable
by adding the --enable-gtk-doc argument to ./configure or ./autogen.sh
- Updated the autogen.sh file so it is not a copied-over obsolete version
of gnome-autogen.sh, but a shell that calls the user's installed
gnome-autogen.sh.
- Removed obsolete .spec file
- Removed obsolete examples/documentation.py file
- Added an example plugin for the LocationWidgetProvider
- Look for python plugins in $XDG_DATA_DIR/nautilus-python/extensions. This
includes ~/.local/share and /usr/share (or whatever $XDG_DATA_DIR is set
to)
0.6.1:
- Look for libpython2.6.so.1.0 instead of libpython2.6.so, the latter
is general available from -devel packages only.
- Re-added the missing spec and pc files
- Free pygobject data directly after using file objects. Stops seg
faults from occurring when nautilus wants to free pygobject data
after Py_Finalize() is called.
0.6.0:
- Remove eel dependency (Vincent Untz)
- Sanitize python search path (Mark Lee)
- Remove gnomevfs dependency and unused code (Daniel Holbach)
- Load python from lib64 in 64 bit multilib distributions (Ted Toth)
- Fix segfault when a plugin doesn't implement the __init__ method
- Added the can_write, get_mount, get_file_type, get_location,
and get_parent_location methods to the NautilusFileInfo object
- Added the NautilusMenu.get_items method
- Updated some example plugins
- Bug fix for some PyThreadState_New segmentation faults
- Use the nautilus prefix by default for distfiles, rather than /usr
- Require nautilus-2.22 and pygobject-2.16 now that we support GIO
0.5.1:
- Add support for location widgets (Tim Cole)
0.5.0:
- Add support for submenus (Lukáš Lalinský, Sylvain Baubeau, Erik Wien)
- Make it work with nautilus 2.22 (Brian Pepple)
- Initialize gnomevfs explicitly (Scott Tsai)
- Compilable with Python 2.5 (Jonathan Rogers)
- Shutdown Python (Gustavo Carneiro)
- Initialize PyGObject/PyGTK/PyGNOMEVFS on demand (Gustavo Carneiro)
0.4.3:
- Make debugging messages a run-time option
- Fix bug in loading extensions from system extensions dir
- Fix crash when no extensions were loaded
0.4.2:
- Make it work again with nautilus >= 2.13.4
- Minor bug fixes
0.4.1:
(missing)
0.4.0:
First public release
## 4.0.alpha (2022-08-12)
- The extension was ported to Nautilus 43 (https://gitlab.gnome.org/GNOME/nautilus-python/-/merge_requests/11)
- Notably, this removes any direct access to GTK widgets from the API. **Most scripts will need to be modified.** Please check the migration guide in the docs on how to update your scripts.
- Switched to Meson build system (https://gitlab.gnome.org/GNOME/nautilus-python/-/merge_requests/10)
- Removed support for Python 2
- Fixed build with `-fno-common` (Andreas Henriksson)
- Added missing parent constructor calls to examples
- Decorated the examples with typehints
- Fixed several memory leaks (Michael Webster)
## 1.2.3 (2019-07-17)
- First release from gitlab
- Fixed open-terminal example extension (Maximillian Schambach)
- Fixed invalid DOAP file category (Andre Klapper)
- Fixed bug https://gitlab.gnome.org/GNOME/nautilus-python/-/issues/3, setting `argv[0]` to thunar
- Fixed bug https://gitlab.gnome.org/GNOME/nautilus-python/-/issues/4, allow overriding the build date to enable reproducible builds
- Removed build warnings (Christian Stadelman)
- Fix to work with python 3.8 (stratakis)
## 1.2.2 (2018-01-14)
- Fixed [bug #792427](https://bugzilla.gnome.org/show_bug.cgi?id=792427), Fix folder string comparison to prevent duplicate extension loading
## 1.2.1 (2018-01-08)
- Fixed [bug #792348](https://bugzilla.gnome.org/show_bug.cgi?id=792348), Fix syntax error when building docs using python3
## 1.2.0 (2018-01-02)
- Added capability to compile with python 3 support using PYTHON environment variable
- Fix [#781232](https://bugzilla.gnome.org/show_bug.cgi?id=781232), Improve extension path loading semantics to follow XDG recommendations
- Fix [#791208](https://bugzilla.gnome.org/show_bug.cgi?id=791208), require Nautilus 3.0 before importing extensions to prevent warnings
- Switch to using gtkdoc mkhtml for generating devhelp2 documentation
## 1.1.0 (2011-10-17)
- Added pygobject3 compatibility. Retained pygobject 2.28.x compatibility.
- Updated extension examples to support pygobject3.
- Fixed [bug #660290](https://bugzilla.gnome.org/show_bug.cgi?id=660290). Updated the FSF address
- Fixed [bug #660288](https://bugzilla.gnome.org/show_bug.cgi?id=660288). Fix autogen warnings with additional macro ACLOCAL_AMFLAGS
- Fixed [bug #660287](https://bugzilla.gnome.org/show_bug.cgi?id=660287). Make the docdir not hard-coded
- Fixed [bug #660286](https://bugzilla.gnome.org/show_bug.cgi?id=660286). Fixes m4 underquoting warning
- Fixed [bug #660283](https://bugzilla.gnome.org/show_bug.cgi?id=660283). Fixes html docs installation issue
- Fixed [bug #653169](https://bugzilla.gnome.org/show_bug.cgi?id=653169). Upated the COPYING file with the most recent GPLv2 license
## 1.0.0 (2011-04-17)
- Use the gobject instrospection dynamic bindings, breaks compatibility for existing extensions.
- For Nautilus3, the `get_toolbar_items` methods have been removed. (Only reporting that change, it isn't up to us). Should still work with Nautilus 2.x annotations.
- No longer look in the old `~/.nautilus/python-extensions` or `/usr/lib/nautilus/extensions2.0/python` folders for extensions. Now look in `~/.local/share/nautilus-python/extensions` or `$XDG_DATA_DIR/nautilus-python/extensions`. Extensions should be arch-independent now.
- General clean up of the repository, removed old .cvsignore files
- Updated the gtk-doc documentation and examples to work with new dynamic bindings.
## 0.7.3 (2011-03-28)
- Use `PyCapsule_Import` for pygobject as well as pygtk
- Fixed bug [#644399](https://bugzilla.gnome.org/show_bug.cgi?id=644399), in the property page example plugin, get the md5sum of the file contents, not the file name
- Removed extraneous `.cvsignore` files
- Fixed the update-file-info-async example plugin
## 0.7.2 (2011-03-04)
- Fix to get the PyCapsule patch to work even if there is no PyCapsule object set up for pygtk.
## 0.7.1 (2011-03-02)
- Fixed AM_CHECK_PYTHON_LIBS usage of test (GNOME [bug #619440](https://bugzilla.gnome.org/show_bug.cgi?id=619440))
- Cleaned up the docs Makefile.am to make it more consistent
- Fix some python3 syntax issues in the python.m4 script
- Add python 2.7 support (GNOME [bug #633171](https://bugzilla.gnome.org/show_bug.cgi?id=633171))
## 0.7.0 (2010-05-21)
- Added methods:
- `nautilus.InfoProvider.update_file_info_full`
- `nautilus.InfoProvider.update_complete_invoke`
- `nautilus.InfoProvider.cancel_update`
- `nautilus.MenuProvider.get_file_items_full`
- `nautilus.MenuProvider.get_background_items_full`
- `nautilus.MenuProvider.get_toolbar_items_full`
- `nautilus.MenuProvider.emit_items_updated_signal`
- Added complete gtk-doc documentation: tutorial and reference. Enable by adding the `--enable-gtk-doc` argument to `./configure` or `./autogen.sh`
- Updated the `autogen.sh` file so it is not a copied-over obsolete version of gnome-autogen.sh, but a shell that calls the user's installed gnome-autogen.sh.
- Removed obsolete .spec file
- Removed obsolete `examples/documentation.py` file
- Added an example plugin for the LocationWidgetProvider
- Look for python plugins in `$XDG_DATA_DIR/nautilus-python/extensions`. This includes `~/.local/share` and `/usr/share` (or whatever `$XDG_DATA_DIR` is set to)
## 0.6.1 (2010-01-19)
- Look for `libpython2.6.so.1.0` instead of `libpython2.6.so`, the latter is general available from -devel packages only.
- Re-added the missing spec and pc files
- Free pygobject data directly after using file objects. Stops segfaults from occurring when nautilus wants to free pygobject data after `Py_Finalize()` is called.
## 0.6.0 (2010-01-15)
- Remove eel dependency (Vincent Untz)
- Sanitize python search path (Mark Lee)
- Remove gnomevfs dependency and unused code (Daniel Holbach)
- Load python from lib64 in 64 bit multilib distributions (Ted Toth)
- Fix segfault when a plugin doesn't implement the `__init__` method
- Added the `can_write`, `get_mount`, `get_file_type`, `get_location`, and `get_parent_location` methods to the `NautilusFileInfo` object
- Added the `NautilusMenu.get_items` method
- Updated some example plugins
- Bug fix for some `PyThreadState_New` segmentation faults
- Use the nautilus prefix by default for distfiles, rather than /usr
- Require nautilus-2.22 and pygobject-2.16 now that we support GIO
## 0.5.2 (2010-03-01)
- Look for libpython2.6.so.1.0 instead of libpython2.6.so, the latter is general available from -devel packages only.
- Remove eel dependency (Vincent Untz)
- Sanitize python search path (Mark Lee)
- Load python from lib64 in 64 bit multilib distributions (Ted Toth)
- Updated some example plugins
- Added explicit gnome-vfs build dependency
- Removed obsolete .spec file
## 0.5.1 (2008-09-16)
- Add support for location widgets (Tim Cole)
## 0.5.0 (2008-01-11)
- Add support for submenus (Lukáš Lalinský, Sylvain Baubeau, Erik Wien)
- Make it work with nautilus 2.22 (Brian Pepple)
- Initialize gnomevfs explicitly (Scott Tsai)
- Compilable with Python 2.5 (Jonathan Rogers)
- Shutdown Python (Gustavo Carneiro)
- Initialize PyGObject/PyGTK/PyGNOMEVFS on demand (Gustavo Carneiro)
## 0.4.3 (2006-02-15)
- Make debugging messages a run-time option
- Fix bug in loading extensions from system extensions dir
- Fix crash when no extensions were loaded
## 0.4.2 (2006-02-10)
- Make it work again with nautilus ≥ 2.13.4
- Minor bug fixes
## 0.4.1 (2005-09-22)
(missing)
## 0.4.0 (2005-05-30)
First public release
libautilus-extension Python bindings
====================================
These are unstable bindings for the nautilus extension library
introduced in Gnome 2.6.
For examples and documentation check the examples sub directory.
Requirements
============
Nautilus 2.32.0
Python 2.x or 3.x
PyGObject 2.28.0
As of v1.2.0 the nautilus-python bindings can be built with either python3
or python2 support. Ensure the $PYTHON environment variable is pointed
at your preferred python executable before running configure or autogen.
Running Extensions
==================
As of nautilus-python 1.2.0, scripts are loaded in the following order:
1. $XDG_DATA_HOME/nautilus-python/extensions (i.e. ~/.local/share/...)
2. nautilus_prefix/share/nautilus-python/extensions (i.e. ~/Development/...)
3. $XDG_DATA_DIRS/nautilus-python/extensions (i.e. /usr/share/...)
Simply copy your python scripts into that folder and restart Nautilus.
Problems
========
It's currently not possible to reload a python script without
restarting nautilus.
Run nautilus with the NAUTILUS_PYTHON_DEBUG=misc environment variable to
print out debug information.
# nautilus-python
This is an extension for Nautilus that allows further extending it with Python scripts with the help of Nautilus’s GObject API.
For examples and documentation check the `examples/` subdirectory.
## Requirements
- Nautilus ≥ 43.beta
- Python 3.x
- PyGObject 3
## Running Extensions
Scripts are loaded in the following order:
1. `$XDG_DATA_HOME/nautilus-python/extensions` (i.e. `~/.local/share/…`)
2. `nautilus_prefix/share/nautilus-python/extensions` (i.e. `~/Development/…`)
3. `$XDG_DATA_DIRS/nautilus-python/extensions` (i.e. `/usr/share/…`)
Simply copy your Python scripts into one of those directories and restart Nautilus.
## Issues
It is currently not possible to reload a Python script without restarting Nautilus.
Run Nautilus with the `NAUTILUS_PYTHON_DEBUG=misc` environment variable to print out debug information.
## License
nautilus-python is released under the terms of the GNU General Public License, either version 2.0 or, at your option, any later version.
This diff is collapsed.
#!/bin/sh
# Wrapper for compilers which do not understand '-c -o'.
scriptversion=2016-01-11.22; # UTC
# Copyright (C) 1999-2017 Free Software Foundation, Inc.
# Written by Tom Tromey <tromey@cygnus.com>.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
# This file is maintained in Automake, please report
# bugs to <bug-automake@gnu.org> or send patches to
# <automake-patches@gnu.org>.
nl='
'
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent tools from complaining about whitespace usage.
IFS=" "" $nl"
file_conv=
# func_file_conv build_file lazy
# Convert a $build file to $host form and store it in $file
# Currently only supports Windows hosts. If the determined conversion
# type is listed in (the comma separated) LAZY, no conversion will
# take place.
func_file_conv ()
{
file=$1
case $file in
/ | /[!/]*) # absolute file, and not a UNC file
if test -z "$file_conv"; then
# lazily determine how to convert abs files
case `uname -s` in
MINGW*)
file_conv=mingw
;;
CYGWIN*)
file_conv=cygwin
;;
*)
file_conv=wine
;;
esac
fi
case $file_conv/,$2, in
*,$file_conv,*)
;;
mingw/*)
file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
;;
cygwin/*)
file=`cygpath -m "$file" || echo "$file"`
;;
wine/*)
file=`winepath -w "$file" || echo "$file"`
;;
esac
;;
esac
}
# func_cl_dashL linkdir
# Make cl look for libraries in LINKDIR
func_cl_dashL ()
{
func_file_conv "$1"
if test -z "$lib_path"; then
lib_path=$file
else
lib_path="$lib_path;$file"
fi
linker_opts="$linker_opts -LIBPATH:$file"
}
# func_cl_dashl library
# Do a library search-path lookup for cl
func_cl_dashl ()
{
lib=$1
found=no
save_IFS=$IFS
IFS=';'
for dir in $lib_path $LIB
do
IFS=$save_IFS
if $shared && test -f "$dir/$lib.dll.lib"; then
found=yes
lib=$dir/$lib.dll.lib
break
fi
if test -f "$dir/$lib.lib"; then
found=yes
lib=$dir/$lib.lib
break
fi
if test -f "$dir/lib$lib.a"; then
found=yes
lib=$dir/lib$lib.a
break
fi
done
IFS=$save_IFS
if test "$found" != yes; then
lib=$lib.lib
fi
}
# func_cl_wrapper cl arg...
# Adjust compile command to suit cl
func_cl_wrapper ()
{
# Assume a capable shell
lib_path=
shared=:
linker_opts=
for arg
do
if test -n "$eat"; then
eat=
else
case $1 in
-o)
# configure might choose to run compile as 'compile cc -o foo foo.c'.
eat=1
case $2 in
*.o | *.[oO][bB][jJ])
func_file_conv "$2"
set x "$@" -Fo"$file"
shift
;;
*)
func_file_conv "$2"
set x "$@" -Fe"$file"
shift
;;
esac
;;
-I)
eat=1
func_file_conv "$2" mingw
set x "$@" -I"$file"
shift
;;
-I*)
func_file_conv "${1#-I}" mingw
set x "$@" -I"$file"
shift
;;
-l)
eat=1
func_cl_dashl "$2"
set x "$@" "$lib"
shift
;;
-l*)
func_cl_dashl "${1#-l}"
set x "$@" "$lib"
shift
;;
-L)
eat=1
func_cl_dashL "$2"
;;
-L*)
func_cl_dashL "${1#-L}"
;;
-static)
shared=false
;;
-Wl,*)
arg=${1#-Wl,}
save_ifs="$IFS"; IFS=','
for flag in $arg; do
IFS="$save_ifs"
linker_opts="$linker_opts $flag"
done
IFS="$save_ifs"
;;
-Xlinker)
eat=1
linker_opts="$linker_opts $2"
;;
-*)
set x "$@" "$1"
shift
;;
*.cc | *.CC | *.cxx | *.CXX | *.[cC]++)
func_file_conv "$1"
set x "$@" -Tp"$file"
shift
;;
*.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO])
func_file_conv "$1" mingw
set x "$@" "$file"
shift
;;
*)
set x "$@" "$1"
shift
;;
esac
fi
shift
done
if test -n "$linker_opts"; then
linker_opts="-link$linker_opts"
fi
exec "$@" $linker_opts
exit 1
}
eat=
case $1 in
'')
echo "$0: No command. Try '$0 --help' for more information." 1>&2
exit 1;
;;
-h | --h*)
cat <<\EOF
Usage: compile [--help] [--version] PROGRAM [ARGS]
Wrapper for compilers which do not understand '-c -o'.
Remove '-o dest.o' from ARGS, run PROGRAM with the remaining
arguments, and rename the output as expected.
If you are trying to build a whole package this is not the
right script to run: please start by reading the file 'INSTALL'.
Report bugs to <bug-automake@gnu.org>.
EOF
exit $?
;;
-v | --v*)
echo "compile $scriptversion"
exit $?
;;
cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \
icl | *[/\\]icl | icl.exe | *[/\\]icl.exe )
func_cl_wrapper "$@" # Doesn't return...
;;
esac
ofile=
cfile=
for arg
do
if test -n "$eat"; then
eat=
else
case $1 in
-o)
# configure might choose to run compile as 'compile cc -o foo foo.c'.
# So we strip '-o arg' only if arg is an object.
eat=1
case $2 in
*.o | *.obj)
ofile=$2
;;
*)
set x "$@" -o "$2"
shift
;;
esac
;;
*.c)
cfile=$1
set x "$@" "$1"
shift
;;
*)
set x "$@" "$1"
shift
;;
esac
fi
shift
done
if test -z "$ofile" || test -z "$cfile"; then
# If no '-o' option was seen then we might have been invoked from a
# pattern rule where we don't need one. That is ok -- this is a
# normal compilation that the losing compiler can handle. If no
# '.c' file was seen then we are probably linking. That is also
# ok.
exec "$@"
fi
# Name of file we expect compiler to create.
cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'`
# Create the lock directory.
# Note: use '[/\\:.-]' here to ensure that we don't use the same name
# that we are using for the .o file. Also, base the name on the expected
# object file name, since that is what matters with a parallel build.
lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d
while true; do
if mkdir "$lockdir" >/dev/null 2>&1; then
break
fi
sleep 1
done
# FIXME: race condition here if user kills between mkdir and trap.
trap "rmdir '$lockdir'; exit 1" 1 2 15
# Run the compile.
"$@"
ret=$?
if test -f "$cofile"; then
test "$cofile" = "$ofile" || mv "$cofile" "$ofile"
elif test -f "${cofile}bj"; then
test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile"
fi
rmdir "$lockdir"
exit $ret
# Local Variables:
# mode: shell-script
# sh-indentation: 2
# eval: (add-hook 'write-file-hooks 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC0"
# time-stamp-end: "; # UTC"
# End:
This diff is collapsed.
/* config.h.in. Generated from configure.ac by autoheader. */
/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define to 1 if you have the <inttypes.h> header file. */
#undef HAVE_INTTYPES_H
/* Define to 1 if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H
/* Define to 1 if you have the <stdint.h> header file. */
#undef HAVE_STDINT_H
/* Define to 1 if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H
/* Define to 1 if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
/* Define to 1 if you have the <sys/stat.h> header file. */
#undef HAVE_SYS_STAT_H
/* Define to 1 if you have the <sys/types.h> header file. */
#undef HAVE_SYS_TYPES_H
/* Define to 1 if you have the <unistd.h> header file. */
#undef HAVE_UNISTD_H
/* Define to the sub-directory where libtool stores uninstalled libraries. */
#undef LT_OBJDIR
/* Nautilus' extensions directory */
#undef NAUTILUS_EXTENSION_DIR
/* Nautilus libdir */
#undef NAUTILUS_LIBDIR
/* Name of package */
#undef PACKAGE
/* Define to the address where bug reports for this package should be sent. */
#undef PACKAGE_BUGREPORT
/* Define to the full name of this package. */
#undef PACKAGE_NAME
/* Define to the full name and version of this package. */
#undef PACKAGE_STRING
/* Define to the one symbol short name of this package. */
#undef PACKAGE_TARNAME
/* Define to the home page for this package. */
#undef PACKAGE_URL
/* Define to the version of this package. */
#undef PACKAGE_VERSION
/* PyGObject major version. */
#undef PYGOBJECT_MAJOR_VERSION
/* PyGObject micro version. */
#undef PYGOBJECT_MICRO_VERSION
/* PyGObject minor version. */
#undef PYGOBJECT_MINOR_VERSION
/* Define to 1 if you have the ANSI C header files. */
#undef STDC_HEADERS
/* Version number of package */
#undef VERSION
This diff is collapsed.
This diff is collapsed.
AC_INIT([nautilus-python], [1.2.3])
AM_CONFIG_HEADER(config.h)
AC_CONFIG_MACRO_DIR([m4])
AM_INIT_AUTOMAKE
AC_SUBST(ACLOCAL_AMFLAGS, "-I m4 -I .")
NAUTILUS_REQUIRED=2.32
AC_PROG_CC
AC_DISABLE_STATIC
AC_PROG_LIBTOOL
dnl Check for pkgconfig first
AC_CHECK_PROG(HAVE_PKGCONFIG, pkg-config, yes, no)
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
dnl Check for gtk-doc
GTK_DOC_CHECK(1.14)
dnl Give error and exit if we don't have pkgconfig
if test "x$HAVE_PKGCONFIG" = "xno"; then
AC_MSG_ERROR(you need to have pkgconfig installed !)
fi
AC_PREFIX_DEFAULT([$(pkg-config --variable=prefix libnautilus-extension || echo /usr)])
dnl **************************************************
dnl * Check for Python
dnl **************************************************
PYG_CHECK_PYTHON_HEADERS(,[AC_MSG_ERROR(could not find Python headers)])
PYG_CHECK_PYTHON_LIBS(,[AC_MSG_ERROR(could not find Python lib)])
if test "`pkg-config --variable=datadir pygobject-3.0`" != "" ; then
PYGOBJECT_VERSION=pygobject-3.0
PYGOBJECT_MAJOR_VERSION=3
PYGOBJECT_MINOR_VERSION=0
PYGOBJECT_MICRO_VERSION=0
else
PYGOBJECT_VERSION=pygobject-2.0
PYGOBJECT_MAJOR_VERSION=2
PYGOBJECT_MINOR_VERSION=28
PYGOBJECT_MICRO_VERSION=2
fi
PYGOBJECT_REQUIRED=$PYGOBJECT_MAJOR_VERSION.$PYGOBJECT_MINOR_VERSION.$PYGOBJECT_MICRO_VERSION
AC_DEFINE_UNQUOTED(PYGOBJECT_MAJOR_VERSION,[$PYGOBJECT_MAJOR_VERSION], [PyGObject major version.])
AC_DEFINE_UNQUOTED(PYGOBJECT_MINOR_VERSION,[$PYGOBJECT_MINOR_VERSION], [PyGObject minor version.])
AC_DEFINE_UNQUOTED(PYGOBJECT_MICRO_VERSION,[$PYGOBJECT_MICRO_VERSION], [PyGObject micro version.])
PKG_CHECK_MODULES(NAUTILUS_PYTHON, [$PYGOBJECT_VERSION >= $PYGOBJECT_REQUIRED
libnautilus-extension >= $NAUTILUS_REQUIRED])
PYGOBJECT_DATADIR=`$PKG_CONFIG --variable=datadir $PYGOBJECT_VERSION`
AC_SUBST(PYGOBJECT_DATADIR)
NAUTILUS_LIBDIR=`$PKG_CONFIG --variable=libdir libnautilus-extension`
AC_SUBST(NAUTILUS_LIBDIR)
AC_DEFINE_UNQUOTED(NAUTILUS_LIBDIR, "$NAUTILUS_LIBDIR", [Nautilus libdir])
dnl ---------------------------------
dnl Get nautilus extensions directory
dnl ---------------------------------
NAUTILUS_EXTENSION_DIR=`$PKG_CONFIG --variable=extensiondir libnautilus-extension`
AC_SUBST(NAUTILUS_EXTENSION_DIR)
AC_DEFINE_UNQUOTED(NAUTILUS_EXTENSION_DIR, "$NAUTILUS_EXTENSION_DIR", [Nautilus' extensions directory])
dnl ---------------------------------
dnl Check for gtk-doc dependencies
dnl ---------------------------------
if test "${enable_gtk_doc}" != no; then
dnl Check for gtkdoc-mkhtml
AC_PATH_PROG([GTKDOC_MKHTML], [gtkdoc-mkhtml])
if test -z "$GTKDOC_MKHTML"; then
echo " disabling generation of docs"
enable_gtk_doc=no
fi
fi
AC_OUTPUT([
Makefile
examples/Makefile
src/Makefile
nautilus-python.pc
docs/Makefile
docs/reference/entities.docbook
])
echo
echo " nautilus-python $VERSION"
echo
echo " Nautilus Prefix: ${prefix}"
echo " PyGObject Version: ${PYGOBJECT_VERSION}"
echo " Python Library: ${PYTHON_LIB_LOC}/${PYTHON_LIB_NAME}"
echo " Documentation: ${enable_gtk_doc}"
echo
This diff is collapsed.
docsdir = $(docdir)
BUILDDIR = $(top_builddir)/docs
REF_VERSION = $(VERSION)
FULL_VERSION = $(VERSION)
XMLdir = $(docsdir)/reference
XML_DATA = \
reference/nautilus-python-ref.xml \
reference/nautilus-python-overview.xml \
reference/nautilus-python-overview-example.xml \
reference/nautilus-python-overview-methods.xml \
reference/nautilus-python-class-reference.xml \
reference/nautilus-python-provider-reference.xml \
reference/nautilus-python-column.xml \
reference/nautilus-python-column-provider.xml \
reference/nautilus-python-menu.xml \
reference/nautilus-python-menu-item.xml \
reference/nautilus-python-menu-provider.xml \
reference/nautilus-python-property-page.xml \
reference/nautilus-python-property-page-provider.xml \
reference/nautilus-python-location-widget-provider.xml \
reference/nautilus-python-file-info.xml \
reference/nautilus-python-info-provider.xml \
reference/nautilus-python-enum-reference.xml \
reference/nautilus-python-operation-result.xml
HTMLdir = $(HTML_DIR)/nautilus-python
HTML_DATA = \
index.html \
index.sgml \
nautilus-python-overview.html \
nautilus-python-overview-example.html \
nautilus-python-overview-methods.html \
nautilus-python-class-reference.html \
nautilus-python-provider-reference.html \
class-nautilus-python-column.html \
class-nautilus-python-column-provider.html \
class-nautilus-python-menu.html \
class-nautilus-python-menu-item.html \
class-nautilus-python-menu-provider.html \
class-nautilus-python-property-page.html \
class-nautilus-python-property-page-provider.html \
class-nautilus-python-location-widget-provider.html \
class-nautilus-python-file-info.html \
class-nautilus-python-info-provider.html \
nautilus-python-enum-reference.html \
enum-nautilus-python-operation-result.html \
nautilus-python.devhelp2 \
up.png up-insensitive.png \
right.png right-insensitive.png \
left.png left-insensitive.png home.png \
style.css
BUILT_SOURCES = \
reference/builddate.xml \
$(HTML_DATA) \
$(XML_DATA)
CLEANFILES = \
nautilus-python-ref.* \
reference/builddate.xml \
$(HTML_DATA)
EXTRA_DIST = \
$(XML_DATA) \
$(HTML_DATA)
REFERENCE_DEPS = \
reference \
$(XML_DATA)
if ENABLE_GTK_DOC
reference/builddate.xml: $(REFERENCE_DEPS)
$(PYTHON) -c "import datetime; import os; import time; print(datetime.datetime.utcfromtimestamp(int(os.environ.get('SOURCE_DATE_EPOCH', time.time()))).date())" > $@
$(HTML_DATA): $(REFERENCE_DEPS) reference/builddate.xml
$(GTKDOC_MKHTML) \
nautilus-python $(srcdir)/reference/nautilus-python-ref.xml \
--path $(BUILDDIR)/reference:$(srcdir)/reference
touch $@
endif
This diff is collapsed.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Nautilus.ColumnProvider: nautilus-python Reference Manual</title>
<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="nautilus-python Reference Manual">
<link rel="up" href="nautilus-python-provider-reference.html" title="Provider Interfaces">
<link rel="prev" href="nautilus-python-provider-reference.html" title="Provider Interfaces">
<link rel="next" href="class-nautilus-python-info-provider.html" title="Nautilus.InfoProvider">
<meta name="generator" content="GTK-Doc V1.28 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><a accesskey="u" href="nautilus-python-provider-reference.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="nautilus-python-provider-reference.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="class-nautilus-python-info-provider.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="class-nautilus-python-column-provider"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2>Nautilus.ColumnProvider</h2>
<p>Nautilus.ColumnProvider — Nautilus.ColumnProvider Reference</p>
</td>
<td class="gallery_image" valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1">
<a name="id-1.5.2.2"></a><h2>Synopsis</h2>
<pre class="classsynopsis"> <span class="ooclass"><span class="classname">Nautilus.ColumnProvider</span></span> {<br><code class="methodsynopsis"> <span class="methodname"><a class="link" href="class-nautilus-python-column-provider.html#method-nautilus-column-provider--get-columns" title="Nautilus.ColumnProvider.get_columns">get_columns</a></span>(<span class="methodparam"></span>);</code><br>}</pre>
</div>
<div class="refsect1">
<a name="description-column-provider"></a><h2>Description</h2>
<p>
If subclassed, Nautilus will request a list of <a class="link" href="class-nautilus-python-column.html" title="Nautilus.Column"><code class="classname">Nautilus.Column</code></a>
objects, which are then displayed when the user is in <code class="literal">List</code> mode.
</p>
<div class="note">An extension sub-classing <a class="link" href="class-nautilus-python-column-provider.html" title="Nautilus.ColumnProvider"><code class="classname">Nautilus.ColumnProvider</code></a>
will almost always want to sub-class <GTKDOCLINK HREF="class-info-provider"><code class="classname">Nautilus.InfoProvider</code></GTKDOCLINK>
as well, since that is how an extension provides information for each item in a directory listing.
</div>
<p>
</p>
<div class="example">
<a name="id-1.5.2.3.3"></a><p class="title"><b>Example 2. Nautilus.ColumnProvider Example</b></p>
<div class="example-contents"><pre class="programlisting">
import os
# A way to get unquote working with python 2 and 3
try:
from urllib import unquote
except ImportError:
from urllib.parse import unquote
from gi.repository import GObject, Nautilus
class ColumnExtension(GObject.GObject, Nautilus.ColumnProvider, Nautilus.InfoProvider):
def __init__(self):
pass
def get_columns(self):
return Nautilus.Column(name="NautilusPython::block_size_column",
attribute="block_size",
label="Block size",
description="Get the block size"),
def update_file_info(self, file):
if file.get_uri_scheme() != 'file':
return
filename = unquote(file.get_uri()[7:])
file.add_string_attribute('block_size', str(os.stat(filename).st_blksize))
</pre></div>
</div>
<br class="example-break">
</div>
<div class="refsect1">
<a name="id-1.5.2.4"></a><h2>Passive Methods</h2>
<div class="refsect2">
<a name="method-nautilus-column-provider--get-columns"></a><h3>Nautilus.ColumnProvider.get_columns</h3>
<pre class="programlisting"><code class="methodsynopsis"><span class="methodname">get_columns</span>(<span class="methodparam"></span>);</code></pre>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody><tr>
<td><p><span class="term"><span class="emphasis"><em>Returns</em></span> :</span></p></td>
<td>a list of <code class="literal">Nautilus.Column</code>
</td>
</tr></tbody>
</table></div>
<p>
The <code class="methodname">get_columns</code>() method returns a list of
<a class="link" href="class-nautilus-python-column.html" title="Nautilus.Column"><code class="classname">Nautilus.Column</code></a>.
</p>
</div>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.28</div>
</body>
</html>