/usr/share/doc/python-webassets-doc/html/upgrading.html is in python-webassets-doc 3:0.11.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Upgrading — webassets 0.11.1 documentation</title>
<link rel="stylesheet" href="_static/classic.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: './',
VERSION: '0.11.1',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="top" title="webassets 0.11.1 documentation" href="index.html" />
<link rel="prev" title="FAQ" href="faq.html" />
</head>
<body role="document">
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="faq.html" title="FAQ"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">webassets 0.11.1 documentation</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="upgrading">
<h1>Upgrading<a class="headerlink" href="#upgrading" title="Permalink to this headline">¶</a></h1>
<p>When upgrading from an older version, you might encounter some backwards
incompatibility. The <code class="docutils literal"><span class="pre">webassets</span></code> API is not stable yet.</p>
<div class="section" id="in-0-10">
<h2>In 0.10<a class="headerlink" href="#in-0-10" title="Permalink to this headline">¶</a></h2>
<ul>
<li><p class="first">The <code class="xref py py-class docutils literal"><span class="pre">Resolver</span></code> API has changed. Rather than being bound to an
environment via the constructor, the individual methods now receive
a <a href="#id1"><span class="problematic" id="id2">``</span></a>ctx` object, which allows access to the environment’s settings.</p>
<p>See <span class="xref std std-ref">the page on implementing resolvers</span>.</p>
</li>
<li><p class="first">The <code class="xref py py-meth docutils literal"><span class="pre">Bundle.build()</span></code> and <code class="xref py py-meth docutils literal"><span class="pre">Bundle.url()</span></code> methods no longer accept
an environment argument. To work with a Bundle that is not attached to
an environment already, use the following syntax instead:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="k">with</span> <span class="n">bundle</span><span class="o">.</span><span class="n">bind</span><span class="p">(</span><span class="n">env</span><span class="p">):</span>
<span class="n">bundle</span><span class="o">.</span><span class="n">build</span><span class="p">()</span>
</pre></div>
</div>
</li>
<li><p class="first">Filters can no longer access a <code class="docutils literal"><span class="pre">self.env</span></code> attribute. It has been renamed
to <code class="docutils literal"><span class="pre">self.ctx</span></code>, which provides a compatible object.</p>
</li>
</ul>
</div>
<div class="section" id="in-0-9">
<h2>In 0.9<a class="headerlink" href="#in-0-9" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>Python 2.5 is no longer supported.</li>
<li>The API of the BaseCache.get() method has changed. It no longer receives
a <code class="docutils literal"><span class="pre">python</span></code> keyword argument. This only affects you if you have
implemented a custom cache class.</li>
</ul>
</div>
<div class="section" id="in-0-8">
<h2>In 0.8<a class="headerlink" href="#in-0-8" title="Permalink to this headline">¶</a></h2>
<ul>
<li><p class="first"><strong>django-assets is no longer included!</strong>
You need to install it’s package separately. See the current
<a class="reference external" href="https://github.com/miracle2k/django-assets">development version</a>.</p>
<div class="admonition warning">
<p class="first admonition-title">Warning</p>
<p>When upgrading, you need to take extra care to rid yourself of the old
version of webassets before installing the separate <code class="docutils literal"><span class="pre">django-assets</span></code>
package. This is to avoid that Python still finds the old <code class="docutils literal"><span class="pre">django_assets</span></code>
module that used to be included with <code class="docutils literal"><span class="pre">webassets</span></code>.</p>
<p>In some cases, even <code class="docutils literal"><span class="pre">pip</span> <span class="pre">uninstall</span> <span class="pre">webassets</span></code> is not enough, and old
<code class="docutils literal"><span class="pre">*.pyc</span></code> files are kept around. I recommend that you delete your old
webassets install manually from the filesystem. To find out where it is
stored, open a Python shell and do:</p>
<div class="last highlight-python"><div class="highlight"><pre><span class="gp">>>> </span><span class="kn">import</span> <span class="nn">webassets</span>
<span class="gp">>>> </span><span class="n">webassets</span>
<span class="go"><module 'webassets' from '/usr/local/lib/python2.7/dist-packages/webassets/src/webassets/__init__.pyc'></span>
</pre></div>
</div>
</div>
</li>
<li><p class="first">Some filters now run in debug mode. Specifically, there are two things that
deserve mention:</p>
<ul>
<li><p class="first"><code class="docutils literal"><span class="pre">cssrewrite</span></code> now runs when <code class="docutils literal"><span class="pre">debug="merge"</span></code>. This is always what is
wanted; it was essentially a bug that this didn’t happen before.</p>
</li>
<li><p class="first">All kinds of compiler-style filters (Sass, less, Coffeescript, JST
templates etc). all now run in debug mode. The presence of such a filter
causes bundles to be merged even while <code class="docutils literal"><span class="pre">debug=True</span></code>.</p>
<p>In practice, if you’ve been using custom bundle <code class="docutils literal"><span class="pre">debug</span></code> values to get
such compilers to run, this will continue to work. Though it can now be
simplified. Code like this:</p>
<div class="highlight-python"><div class="highlight"><pre>Bundle(
Bundle('*.coffee', filters='coffeescript', debug=False)
filters='jsmin')
</pre></div>
</div>
<p>can be replaced with:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">Bundle</span><span class="p">(</span><span class="s">'*.coffee'</span><span class="p">,</span> <span class="n">filters</span><span class="o">=</span><span class="s">'coffeescript,jsmin'</span><span class="p">)</span>
</pre></div>
</div>
<p>which has the same effect, which is that during debugging, Coffeescript
will be compiled, but not minimized. This also allows you to define bundles
that use compilers from within the templates tags, because nesting is no
longer necessary.</p>
<p>However, if you need to combine Coffeescript files (or other files needing
compiling) with regular CSS or JS files, nesting is still required:</p>
<div class="highlight-python"><div class="highlight"><pre>Bundle('*.js'
Bundle('*.coffee', filters='coffeescript'),
filters='jsmin')
</pre></div>
</div>
<p>If for some reason you do not want these compilers to run, you may still
use a manual <code class="docutils literal"><span class="pre">debug</span></code> value to override the behavior. A case where this
is useful is the <code class="docutils literal"><span class="pre">less</span></code> filter, which can be compiled in the browser:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">Bundle</span><span class="p">(</span><span class="s">'*.less'</span><span class="p">,</span> <span class="n">filters</span><span class="o">=</span><span class="s">'less'</span><span class="p">,</span> <span class="n">debug</span><span class="o">=</span><span class="bp">True</span><span class="p">)</span>
</pre></div>
</div>
<p>Here, as long as the environment is in debug mode, the bundle will output
the source urls, despite the <code class="docutils literal"><span class="pre">less</span></code> filter normally forcing a merge.</p>
</li>
</ul>
<p>As part of this new feature, the handling of nested bundle debug values
has changed such that in rare cases you may see a different outcome. In
the unlikely case that you are using these a lot, the rule is simple: The
debug level can only ever be decreased. Child bundles cannot cannot do
“more debugging” than their parent, and if <code class="docutils literal"><span class="pre">Environment.debug=False</span></code>,
all bundle debug values are effectively ignored.</p>
</li>
<li><p class="first">The internal class names of filters have been renamed. For example,
<code class="docutils literal"><span class="pre">JSMinFilter</span></code> is now simply <code class="docutils literal"><span class="pre">JSMin</span></code>. This only affects you if you
reference these classes directly, rather than using their id (such as
<code class="docutils literal"><span class="pre">jsmin</span></code>), which should be rare.</p>
</li>
<li><p class="first">Removed the previously deprecated <code class="docutils literal"><span class="pre">rebuild</span></code> alias for the <code class="docutils literal"><span class="pre">build</span></code> command.</p>
</li>
<li><p class="first">Subtly changed how the <code class="docutils literal"><span class="pre">auto_build</span></code> setting affects the
<code class="xref py py-meth docutils literal"><span class="pre">Bundle.build()</span></code> method: It doesn’t anymore. Instead, the setting now
only works on the level of <code class="xref py py-meth docutils literal"><span class="pre">Bundle.urls()</span></code>. The new behaviour is more
consistent, makes more sense, and simplifies the code.</p>
<p>The main backwards-incompatiblity caused by this is that when
<code class="docutils literal"><span class="pre">environment.auto_build=False</span></code>, and you are calling <code class="docutils literal"><span class="pre">bundle.build()</span></code>
without specifying an explicit <code class="docutils literal"><span class="pre">force</span></code> argument, it used to be the case
that <code class="docutils literal"><span class="pre">force=True</span></code> was assumed, i.e. the bundle was built without looking
at the timestamps to see if a rebuild is necessary. Now, the timestamps will
be checked, unless <code class="docutils literal"><span class="pre">force=True</span></code> is explicitly given.</p>
<p>In case you don’t want to pass <code class="docutils literal"><span class="pre">force=True</span></code>, you can instead also set
the <code class="xref py py-attr docutils literal"><span class="pre">Environment.updater</span></code> property to <code class="docutils literal"><span class="pre">False</span></code>; without an updater
to check timestamps, every <code class="docutils literal"><span class="pre">build()</span></code> call will act as if <code class="docutils literal"><span class="pre">force=True</span></code>.</p>
<p><strong>Note</strong>: This only affects you if you work with the <code class="xref py py-meth docutils literal"><span class="pre">Bundle.build()</span></code>
and <code class="xref py py-meth docutils literal"><span class="pre">Bundle.url()</span></code> methods directly. The behavior of the command line
interface, or the template tags is not affected.</p>
</li>
<li><p class="first">The implementation of the <code class="xref py py-class docutils literal"><span class="pre">CommandLineEnvironment</span></code> has changed, and
each command is now a separate class. If you have been subclassing
<code class="xref py py-class docutils literal"><span class="pre">CommandLineEnvironment</span></code> to override individual command methods like
<code class="xref py py-meth docutils literal"><span class="pre">CommandLineEnvironment.build()</span></code>, you need to update your code.</p>
</li>
<li><p class="first">The <code class="xref py py-class docutils literal"><span class="pre">JavaMixin</span></code> helper class to implement Java-based filters has been
removed, and in it’s stead there is now a <code class="xref py py-class docutils literal"><span class="pre">JavaTool</span></code> base class that
can be used.</p>
</li>
<li><p class="first">The code to resolve bundle contents has been refactored. As a result, the
behavior of the semi-internal method <code class="xref py py-meth docutils literal"><span class="pre">Bundle.resolve_contents()</span></code> has
changed slightly; in addition, the
<code class="xref py py-meth docutils literal"><span class="pre">Environment._normalize_source_path()</span></code> method used mainly by
extensions like <code class="docutils literal"><span class="pre">Flask-Assets</span></code> has been removed. Instead, extensions now
need to implement a custom <code class="xref py py-class docutils literal"><span class="pre">Resolver</span></code>. The
<code class="xref py py-class docutils literal"><span class="pre">Evironment.absurl</span></code> method has also disappeared, and replacing it
can now be done via a custom <code class="xref py py-class docutils literal"><span class="pre">Resolver`</span></code> class.</p>
</li>
<li><p class="first"><code class="xref py py-attr docutils literal"><span class="pre">Environment.directory</span></code> now always returns an absolute path; if a
relative path is stored, it is based off on the current working directory.
This spares <em>a lot</em> of calls to <code class="docutils literal"><span class="pre">os.abspath</span></code> throughout the code. If you
need the original value you can always use
<code class="docutils literal"><span class="pre">environment.config['directory']</span></code>.</p>
</li>
<li><p class="first">If the <code class="docutils literal"><span class="pre">JST_COMPILER</span></code> option of the <code class="docutils literal"><span class="pre">jst</span></code> filter is set to <code class="docutils literal"><span class="pre">False</span></code>
(as opposed to the default value, <code class="docutils literal"><span class="pre">None</span></code>), the templates will now be
output as raw strings. Before, <code class="docutils literal"><span class="pre">False</span></code> behaved like <code class="docutils literal"><span class="pre">None</span></code> and used
the builtin compiler.</p>
</li>
<li><p class="first">The API of the <code class="docutils literal"><span class="pre">concat()</span></code> filter method has changed. Instead of a
list of hunks, it is now given a list of 2-tuples of
<code class="docutils literal"><span class="pre">(hunk,</span> <span class="pre">info_dict)</span></code>.</p>
</li>
<li><p class="first">The internal <code class="docutils literal"><span class="pre">JSTTemplateFilter</span></code> base class has changed API.
- concat filter
- jst handlebar filters have changed, use concat, base class has changed</p>
</li>
</ul>
</div>
<div class="section" id="in-0-7">
<h2>In 0.7<a class="headerlink" href="#in-0-7" title="Permalink to this headline">¶</a></h2>
<p>There are some significant backwards incompatible changes in this release.</p>
<ul class="simple">
<li>The <code class="docutils literal"><span class="pre">Environment.updater</span></code> property (corresponds to the
<code class="docutils literal"><span class="pre">ASSETS_UPDATER</span></code> setting) can no longer be set to <code class="docutils literal"><span class="pre">False</span></code> or
<code class="docutils literal"><span class="pre">"never"</span></code> in order to disable the automatic rebuilding. Instead, this
now needs to be done using <code class="docutils literal"><span class="pre">Environment.auto_build</span></code>, or the corresponding
<code class="docutils literal"><span class="pre">ASSETS_AUTO_BUILD</span></code> setting.</li>
<li>The <code class="docutils literal"><span class="pre">Environment.expire</span></code> (<code class="docutils literal"><span class="pre">ASSETS_EXPIRE</span></code>) option as been renamed to
<code class="docutils literal"><span class="pre">Environment.url_expire</span></code> (<code class="docutils literal"><span class="pre">ASSETS_URL_EXPIRE</span></code>), and the default value
is now <code class="docutils literal"><span class="pre">True</span></code>.</li>
<li>To disable automatic building, set the new <code class="docutils literal"><span class="pre">Environment.auto_build</span></code>
(<code class="docutils literal"><span class="pre">ASSETS_AUTO_BUILD</span></code>) option to <code class="docutils literal"><span class="pre">False</span></code>. Before, this was done via
the <code class="docutils literal"><span class="pre">Environment.updater</span></code>, which is now deprecated.</li>
</ul>
<p>Other changes:</p>
<ul class="simple">
<li>If <code class="docutils literal"><span class="pre">Environment.auto_build</span></code> is disabled, the API of Bundle.build()
now assumes a default value of <code class="docutils literal"><span class="pre">True</span></code> for the <code class="docutils literal"><span class="pre">force</span></code> argument.
This should not cause any problems, since it is the only call signature
that really makes sense in this case.</li>
<li>The former <code class="docutils literal"><span class="pre">less</span></code> filter, based on the old Ruby version of lessCSS
(still available as the 1.x Ruby gems, but no longer developed) has been
renamed <code class="docutils literal"><span class="pre">less_ruby</span></code>, and <code class="docutils literal"><span class="pre">less</span></code> now uses the new NodeJS/Javascript
implementation, which a while ago superseded the Ruby one.</li>
<li>The <code class="docutils literal"><span class="pre">rebuild</span></code> command (of the command line mode) has been renamed to
<code class="docutils literal"><span class="pre">build</span></code>.</li>
<li>The command line interface now requires the external dependency
<code class="docutils literal"><span class="pre">argparse</span></code> on Python versions 2.6 and before. <code class="docutils literal"><span class="pre">argparse</span></code> is included
with Python starting with version 2.7.</li>
<li><code class="docutils literal"><span class="pre">PythonLoader.load_bundles()</span></code> now returns a dict with the bundle names
as keys, rather than a list.</li>
<li>Filters now receive new keyword arguments. The API now officially requires
filters to accept arbitrary <code class="docutils literal"><span class="pre">**kwargs</span></code> for compatibility with future
versions. While the documentation has always suggested <code class="docutils literal"><span class="pre">**kwargs</span></code> be used,
not all builtin filters followed this rule. Your custom filters may need
updating as well.</li>
<li>Filter classes now longer get an auto-generated name. If you have a custom
filter and have not explicitly given it a name, you need to do this now if
you want to register the filter globally.</li>
<li><code class="docutils literal"><span class="pre">django_assets</span></code> no longer tries to load a global <code class="docutils literal"><span class="pre">assets.py</span></code> module (it
will still find bundles defined in application-level <code class="docutils literal"><span class="pre">assets.py</span></code> files). If
you want to define bundles in other modules, you now need to list those
explicitly in the <span class="xref std std-ref">ASSETS_MODULES</span> setting.</li>
</ul>
</div>
<div class="section" id="in-0-6">
<h2>In 0.6<a class="headerlink" href="#in-0-6" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>The <code class="docutils literal"><span class="pre">Environment.updater</span></code> class no longer support custom callables.
Instead, you need to subclass <code class="docutils literal"><span class="pre">BaseUpdater</span></code>. Nobody is likely to use
this feature though.</li>
<li>The cache is no longer debug-mode only. If you enable
<code class="docutils literal"><span class="pre">Environment.cache</span></code> (<code class="docutils literal"><span class="pre">ASSETS_CACHE</span></code> in <code class="docutils literal"><span class="pre">django-assets</span></code>),
the cache will be enabled regardless of the
<code class="docutils literal"><span class="pre">Environment.debug</span></code>/<code class="docutils literal"><span class="pre">ASSETS_DEBUG</span></code> option. If you want the old
behavior, you can easily configure it manually.</li>
<li>The <code class="docutils literal"><span class="pre">Bundle.build</span></code> method no longer takes the <code class="docutils literal"><span class="pre">no_filters</span></code>
argument. This was always intended for internal use and its existence
not advertised, so its removal shouldn’t cause too many problems.</li>
<li>The <code class="docutils literal"><span class="pre">Bundle.build</span></code> method now returns a list of <code class="docutils literal"><span class="pre">FileHunk</span></code> objects,
rather than a single one. It now works for container bundles (bundles
which only have other bundles for children, not files), rather than
raising an exception.</li>
<li>The <code class="docutils literal"><span class="pre">rebuild</span></code> command now ignores a <code class="docutils literal"><span class="pre">debug=False</span></code> setting, and
forces a build in production mode instead.</li>
</ul>
</div>
<div class="section" id="in-0-4">
<h2>In 0.4<a class="headerlink" href="#in-0-4" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>Within <code class="docutils literal"><span class="pre">django_assets</span></code>. the semantics of the <code class="docutils literal"><span class="pre">debug</span></code> setting have
changed again. It once again allows you to specifically enable debug mode
for the assets handling, irrespective of Django’s own <code class="docutils literal"><span class="pre">DEBUG</span></code> setting.</li>
<li><code class="docutils literal"><span class="pre">RegistryError</span></code> is now <code class="docutils literal"><span class="pre">RegisterError</span></code>.</li>
<li>The <code class="docutils literal"><span class="pre">ASSETS_AUTO_CREATE</span></code> option no longer exists. Instead, automatic
creation of bundle output files is now bound to the <code class="docutils literal"><span class="pre">ASSETS_UPDATER</span></code>
setting. If it is <code class="docutils literal"><span class="pre">False</span></code>, i.e. automatic updating is disabled, then
assets won’t be automatically created either.</li>
</ul>
</div>
<div class="section" id="in-0-2">
<h2>In 0.2<a class="headerlink" href="#in-0-2" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>The filter API has changed. Rather than defining an <code class="docutils literal"><span class="pre">apply</span></code> method and
optionally an <code class="docutils literal"><span class="pre">is_source_filter</span></code> attribute, those now have been replaced
by <code class="docutils literal"><span class="pre">input()</span></code> and <code class="docutils literal"><span class="pre">output()</span></code> methods. As a result, a single filter can
now act as both an input and an output filter.</li>
</ul>
</div>
<div class="section" id="in-0-1">
<h2>In 0.1<a class="headerlink" href="#in-0-1" title="Permalink to this headline">¶</a></h2>
<ul>
<li><p class="first">The semantics of the <code class="docutils literal"><span class="pre">ASSETS_DEBUG</span></code> setting have changed. In 0.1,
setting this to <code class="docutils literal"><span class="pre">True</span></code> meant <em>enable the django-assets debugging mode</em>.
However, <code class="docutils literal"><span class="pre">django-assets</span></code> now follows the default Django <code class="docutils literal"><span class="pre">DEBUG</span></code>
setting, and <code class="docutils literal"><span class="pre">ASSETS_DEBUG</span></code> should be understood as meaning <em>how to
behave when in debug mode</em>. See <span class="xref std std-ref">ASSETS_DEBUG</span>
for more information.</p>
</li>
<li><p class="first"><code class="docutils literal"><span class="pre">ASSETS_AUTO_CREATE</span></code> now causes an error to be thrown if due it it
being disabled a file cannot be created. Previously, it caused
the source files to be linked directly (as if debug mode were active).</p>
<p>This was done due to <code class="docutils literal"><span class="pre">Explicit</span> <span class="pre">is</span> <span class="pre">better</span> <span class="pre">than</span> <span class="pre">implicit</span></code>, and for
security considerations; people might trusting their comments to be
removed. If it turns out to be necessary, the functionality to fall
back to source could be added again in a future version through a
separate setting.</p>
</li>
<li><p class="first">The YUI Javascript filter can no longer be referenced via <code class="docutils literal"><span class="pre">yui</span></code>.
Instead, you need to explicitly specify which filter you want to use,
<code class="docutils literal"><span class="pre">yui_js</span></code> or <code class="docutils literal"><span class="pre">yui_css</span></code>.</p>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Upgrading</a><ul>
<li><a class="reference internal" href="#in-0-10">In 0.10</a></li>
<li><a class="reference internal" href="#in-0-9">In 0.9</a></li>
<li><a class="reference internal" href="#in-0-8">In 0.8</a></li>
<li><a class="reference internal" href="#in-0-7">In 0.7</a></li>
<li><a class="reference internal" href="#in-0-6">In 0.6</a></li>
<li><a class="reference internal" href="#in-0-4">In 0.4</a></li>
<li><a class="reference internal" href="#in-0-2">In 0.2</a></li>
<li><a class="reference internal" href="#in-0-1">In 0.1</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="faq.html"
title="previous chapter">FAQ</a></p>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/upgrading.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="faq.html" title="FAQ"
>previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">webassets 0.11.1 documentation</a> »</li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2009, 2010, Michael Elsdörfer.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.3.3.
</div>
</body>
</html>
|