Definindo o caminho do Python para a versão do tronco do Django

Question

Estou tentando executar os testes de unidade para a versão de tronco do Django. Eu também tenho uma versão do Django instalada no meu sistema que eu instalei via apt-get install .

Como posso alterar o caminho do Python para apontar para a versão do tronco do Django?

    

Answer 1

Do bash (ou outro shell), você pode manipular o $ PYTHONPATH para apontar para o diretório pai, por exemplo, echo $PYTHONPATH e export PYTHONPATH="/newhome/django_x.x/trunk"

Isso irá prefixar os caminhos dados à lista de caminhos existentes do python.

python.org :

For example, if PYTHONPATH is set to /www/python:/opt/py, the search path will begin with

['/www/python','/opt/py']

(Note that directories must exist in order to be added to sys.path; the site module removes paths that don’t exist.)

Dentro do python, você também pode alterar o sys.path ( import sys se você não tiver) para apontar para o ramo de teste.

Exemplo de python.org :

$ python
Python 2.2 (#11, Oct  3 2002, 13:31:27)
[GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', '/usr/local/lib/python2.3', '/usr/local/lib/python2.3/plat-linux2',
 '/usr/local/lib/python2.3/lib-tk', '/usr/local/lib/python2.3/lib-dynload',
 '/usr/local/lib/python2.3/site-packages']
>>>

Para adicionar um caminho, use algo como:

sys.path.append('/workingdir/python/')

Um exemplo centrado no Django de djangotricks (blog):

import os, sys

SVN_PATH = os.path.abspath(os.path.join(os.path.dirname(__file__), "..", ".."))
DJANGO_PATH = os.path.join(SVN_PATH, "django_src", "trunk")
PROJECT_PATH = os.path.join(SVN_PATH, "myproject", "trunk")

sys.path += [DJANGO_PATH, PROJECT_PATH]

Além disso, a menos que você tenha suprimido o comportamento, o python carrega site.py na execução. Assim, você também pode editar o arquivo site.py , por exemplo, /usr/lib/python2.7/site.py :

Os comentários do arquivo site.py também são instrutivos.

$ more /usr/lib/python2.7/site.py

"""Append module search paths for third-party packages to sys.path.

****************************************************************
* This module is automatically imported during initialization. *
****************************************************************

In earlier versions of Python (up to 1.5a3), scripts or modules that
needed to use site-specific modules would place ''import site''
somewhere near the top of their code.  Because of the automatic
import, this is no longer necessary (but code that does it still
works).

This will append site-specific paths to the module search path.  On
Unix (including Mac OSX), it starts with sys.prefix and
sys.exec_prefix (if different) and appends
lib/python<version>/site-packages as well as lib/site-python.
On other platforms (such as Windows), it tries each of the
prefixes directly, as well as with lib/site-packages appended.  The
resulting directories, if they exist, are appended to sys.path, and
also inspected for path configuration files.

For Debian and derivatives, this sys.path is augmented with directories
for packages distributed within the distribution. Local addons go
into /usr/local/lib/python<version>/dist-packages,
Debian addons
install into /usr/{lib,share}/python<version>/dist-packages.
/usr/lib/python<version>/site-packages
is not used.

A path configuration file is a file whose name has the form
<package>.pth; its contents are additional directories (one per line)
to be added to sys.path.  Non-existing directories (or
non-directories) are never added to sys.path; no directory is added to
sys.path more than once.  Blank lines and lines beginning with
'#' are skipped. Lines starting with 'import' are executed.

For example, suppose sys.prefix and sys.exec_prefix are set to
/usr/local and there is a directory
/usr/local/lib/python2.5/site-packages
with three subdirectories, foo, bar and spam, and two path
configuration files, foo.pth and bar.pth.  Assume foo.pth contains the
following:

  # foo package configuration
  foo
  bar
  bletch

and bar.pth contains:

  # bar package configuration
  bar

Then the following directories are added to sys.path, in this order:

  /usr/local/lib/python2.5/site-packages/bar
  /usr/local/lib/python2.5/site-packages/foo

Note that bletch is omitted because it doesn't exist; bar precedes
foo
because bar.pth comes alphabetically before foo.pth; and
spam is
omitted because it is not mentioned in either path configuration
file.

After these path manipulations, an attempt is made to import a module
named sitecustomize, which can perform arbitrary additional
site-specific customizations.  If this import fails with an
ImportError exception, it is silently ignored.

Referências:
caminho de pesquisa python.org docs, v2.7
python.org docs, caminho de pesquisa da v3
Djangotricks blog, uma observação sobre caminhos python
Martin Jansen: Arquivos de configurações do Django para desenvolvimento e produção

    

Answer 2

Boa pergunta. Você pode resolver esse problema com python. Abra o interpretador python e

Python 2.6
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print sys.path
['', '/usr/lib/python24.zip', '/usr/lib/python2.4',
'/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk',
'/usr/lib/python2.4/lib-dynload', '/usr/local/lib/python2.4/site-packages',
'/usr/lib/python2.4/site-packages', '/usr/lib/site-python']

Para mudar o caminho, basta anexar / anexar entradas ao sys.path, que é normal Lista de Python, por exemplo

>>> sys.path.append('/path/to/django/trunk')
>>> sys.path.insert(0, '/path/to/django/trunk')

Qualquer um desses comandos deve adicioná-lo ao seu caminho.