1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
.. index::
single: converting a BFG app
single: bfg2pyramid
.. _converting_a_bfg_app:
Converting a :mod:`repoze.bfg` Application to :mod:`pyramid`
============================================================
Prior iterations of :mod:`pyramid` were released as a package named
:mod:`repoze.bfg`. :mod:`repoze.bfg` users are encouraged to upgrade
their deployments to :mod:`pyramid`, as, after the first final release
of :mod:`pyramid`, further feature development on :mod:`repoze.bfg`
will cease.
Most existing :mod:`repoze.bfg` applications can be converted to a
:mod:`pyramid` application in a completely automated fashion.
However, if your application depends on packages which are not "core"
parts of :mod:`repoze.bfg` but which nonetheless have ``repoze.bfg``
in their names (e.g. ``repoze.bfg.skins``,
``repoze.bfg.traversalwrapper``, ``repoze.bfg.jinja2``), you will need
to find an analogue for each. For example, by the time you read this,
there will be a ``pyramid_jinja2`` package, which can be used instead
of ``repoze.bfg.jinja2``. If an analogue does not seem to exist for a
``repoze.bfg`` add-on package that your application uses, please email
the `Pylons-discuss <http://groups.google.com/group/pylons-discuss>`_
maillist; we'll convert the package to a :mod:`pyramid` analogue for
you.
Here's how to convert a :mod:`repoze.bfg` application to a
:mod:`pyramid` application:
#. Ensure that your application works under :mod:`repoze.bfg` *version
1.3 or better*. See
`http://docs.repoze.org/bfg/1.3/narr/install.html
<http://docs.repoze.org/bfg/1.3/narr/install.html>`_ for
:mod:`repoze.bfg` 1.3 installation instructions. If your
application has an automated test suite, run it while your
application is using :mod:`repoze.bfg` 1.3+. Otherwise, test it
manually. It is only safe to proceed to the next step once your
application works under :mod:`repoze.bfg` 1.3+.
If your application has a proper set of dependencies, and a
standard automated test suite, you might test your
:mod:`repoze.bfg` application against :mod:`repoze.bfg` 1.3 like
so:
.. code-block:: bash
$ bfgenv/bin/python setup.py test
``bfgenv`` above will be the virtualenv into which you've installed
:mod:`repoze.bfg` 1.3.
#. Install :mod:`pyramid` into a *separate* virtualenv as per the
instructions in :ref:`installing_chapter`. The :mod:`pyramid`
virtualenv should be separate from the one you've used to install
:mod:`repoze.bfg`. A quick way to do this:
.. code-block:: bash
$ cd ~
$ virtualenv --no-site-packages pyramidenv
$ cd pyramidenv
$ bin/easy_install pyramid
#. Put a *copy* of your :mod:`repoze.bfg` application into a temporary
location (perhaps by checking a fresh copy of the application out
of a version control repository). For example:
.. code-block:: bash
$ cd /tmp
$ svn co http://my.server/my/bfg/application/trunk bfgapp
#. Use the ``bfg2pyramid`` script present in the ``bin`` directory of
the :mod:`pyramid` virtualenv to convert all :mod:`repoze.bfg`
Python import statements into compatible :mod:`pyramid` import
statements. ``bfg2pyramid`` will also fix ZCML directive usages of
common :mod:`repoze.bfg` directives. You invoke ``bfg2pyramid`` by
passing it the *path* of the copy of your application. The path
passed should contain a "setup.py" file, representing your
:mod:`repoze.bfg` application's setup script. ``bfg2pyramid`` will
change the copy of the application *in place*.
.. code-block:: bash
$ ~/pyramidenv/bfg2pyramid /tmp/bfgapp
``bfg2pyramid`` will convert the following :mod:`repoze.bfg`
application aspects to :mod:`pyramid` compatible analogues:
- Python ``import`` statements naming :mod:`repoze.bfg` APIs will
be converted to :mod:`pyramid` compatible ``import`` statements.
Every Python file beneath the top-level path will be visited and
converted recursively, except Python files which live in
directories which start with a ``.`` (dot).
- Each ZCML file found (recursively) within the path will have the
default ``xmlns`` attribute attached to the ``configure`` tag
changed from ``http://namespaces.repoze.org/bfg`` to
``http://pylonshq.com/pyramid``. Every ZCML file beneath the
top-level path (files ending with ``.zcml``) will be visited and
converted recursively, except ZCML files which live in
directories which start with a ``.`` (dot).
- ZCML files which contain directives that have attributes which
name a ``repoze.bfg`` API module or attribute of an API module
(e.g. ``context="repoze.bfg.exceptions.NotFound"``) will be
converted to :mod:`pyramid` compatible ZCML attributes
(e.g. ``context="pyramid.exceptions.NotFound``). Every ZCML file
beneath the top-level path (files ending with ``.zcml``) will be
visited and converted recursively, except ZCML files which live
in directories which start with a ``.`` (dot).
#. Edit the ``setup.py`` file of the application you've just converted
(if you've been using the example paths, this will be
``/tmp/bfgapp/setup.py``) to depend on the ``pyramid`` distribution
instead the of ``repoze.bfg`` distribution in its
``install_requires`` list. If you used a ``paster`` template to
create the :mod:`repoze.bfg` application, you can do so by changing
the ``requires`` line near the top of the ``setup.py`` file. The
original may look like this:
.. code-block:: text
requires = ['repoze.bfg', ... other dependencies ...]
Edit the ``setup.py`` so it has:
.. code-block:: text
requires = ['pyramid', ... other dependencies ...]
All other install-requires and tests-requires dependencies save for
the one on ``repoze.bfg`` can remain the same.
#. Convert any ``install_requires`` dependencies your application has
on other add-on packages which have ``repoze.bfg`` in their names
to :mod:`pyramid` compatible analogues (e.g. ``repoze.bfg.jinja2``
should be replaced with ``pyramid_jinja2``). You may need to
adjust configuration options and/or imports in your
:mod:`repoze.bfg` application after replacing these add-ons. Read
the documentation of the :mod:`pyramid` add-on package for
information.
#. *Only if you use ZCML and add-ons which use ZCML*: The default
``xmlns`` of the ``configure`` tag in ZCML has changed. The
``bfg2pyramid`` script effects the default namespace change (it
changes the ``configure`` tag default ``xmlns`` from
``http://namespaces.repoze.org/bfg`` to
``http://pylonshq.com/pyramid``).
This means that uses of add-ons which define ZCML directives in the
``http://namespaces.repoze.org/bfg`` namespace will begin to "fail"
(they're actually not really failing, but your ZCML assumes that
they will always be used within a ``configure`` tag which names the
``http://namespaces.repoze.org/bfg`` namespace as its default
``xmlns``). Symptom: when you attempt to start the application, an
error such as ``ConfigurationError: ('Unknown directive',
u'http://namespaces.repoze.org/bfg', u'workflow')`` is printed to
the console and the application fails to start. In such a case,
either add an ``xmlns="http://namespaces.repoze.org/bfg"``
attribute to each tag which causes a failure, or define a namespace
alias in the configure tag and prefix each failing tag. For
example, change this "failing" tag instance::
<configure xmlns="http://pylonshq.com/pyramid">
<failingtag attr="foo"/>
</configure>
To this, which will begin to succeed::
<configure xmlns="http://pylonshq.com/pyramid"
xmlns:bfg="http://namespaces.repoze.org/bfg">
<bfg:failingtag attr="foo"/>
</configure>
#. Retest your application using :mod:`pyramid`. This might be as
easy as:
.. code-block:: bash
$ cd /tmp/bfgapp
$ ~/pyramidenv/bin/python setup.py test
#. Fix any test failures.
#. Start using the converted version of your application. Celebrate.
|
