Core migration

How to update your code to new versions

Home › Python software › Core › MigrationText · XIST · FO · PDF

Migrating to ll-core 1.6

Handling of file data and file metadata in ll.url has been largely rewritten. The most significant visible change is that the ReadResource properties resdata, resheaders, imagesize, mimetype, encoding and finalurl are methods now. A few properties have been turned into methods and have been renamed: lastmodified has been renamed to mdate, contentlength has been renamed to size and stats has been renamed to stat.

Migrating to ll-core 1.5

The functions ll.url.Dirname and ll.url.Filename have been removed (use ll.url.Dir and ll.url.File instead).

The methods ll.url.URL.isLocal and ll.url.URL.asFilename have been removed (use ll.url.URL.islocal and ll.url.URL.local instead).

Migrating to ll-core 1.3

ll.make has been largely rewritten, so you have to adapt your make scripts. For examples demonstrating how to do this, take a look at either the small example in the module itself or the make script for the website.

Migrating to ll-core 1.2

Processing instruction targets in ll.xpit now require whitespace after the target name. This means that you have to replace <?=foo?> with <?= foo?> in your xpit strings.

Migrating to ll-core 1.1

If you've been using TOXICAction from ll.make, you have to use a DecodeAction before the TOXICAction to decode the str object into a unicode object and use a EncodeAction afterwards to encode it again as the constructor of TOXICAction no longer takes an encoding argument, but operates on unicode strings directly.

Migrating to ll-core 1.0

The content of the ll module has been move to ll.misc, so you have to replace e.g. ll.notimplemented with misc.notimplemented etc.