Viewing File: /usr/local/cpanel/3rdparty/mailman/Mailman/versions.pyc
ó
¾}´^c @ sÑ d Z d d l Z d d l m Z m Z d d l m Z d d l m Z d d l m Z d d l m
Z
d d l m Z d d l
m Z d
„ Z d „ Z g Z d „ Z d
„ Z d „ Z d „ Z d „ Z d S( sR Routines which rectify an old mailing list with current structure.
The MailList.CheckVersion() method looks for an old .data_version setting in
the loaded structure, and if found calls the Update() routine from this
module, supplying the list and the state last loaded from storage. The state
is necessary to distinguish from default assignments done in the .InitVars()
methods, before .CheckVersion() is called.
For new versions you should add sections to the UpdateOldVars() and the
UpdateOldUsers() sections, to preserve the sense of settings across structural
changes. Note that the routines have only one pass - when .CheckVersions()
finds a version change it runs this routine and then updates the data_version
number of the list, and then does a .Save(), so the transformations won't be
run again until another version change is detected.
iÿÿÿÿN( t ListTypet
StringType( t mm_cfg( t Utils( t Message( t _BounceInfo( t UNKNOWN( t syslogc C sC t | ƒ t | ƒ t | ƒ t | | ƒ t | ƒ t | ƒ d S( sH Dispose of old vars and user options, mapping to new ones when suitable.N( t
ZapOldVarst UpdateOldUserst NewVarst
UpdateOldVarst CanonicalizeUserOptionst NewRequestsDatabase( t lt stored_state( ( s6 /usr/local/cpanel/3rdparty/mailman/Mailman/versions.pyt Update1 s
c
C s4 x- d D]% } t | | ƒ r t | | ƒ q q Wd S( Nt
num_spawnst filter_progt clobber_datet public_archive_file_dirt private_archive_file_dirt archive_directoryt minimum_removal_datet' minimum_post_count_before_bounce_actiont automatic_bounce_actiont max_posts_between_bounces(
R R R R R R R R R R ( t hasattrt delattr( t mlistt name( ( s6 /usr/local/cpanel/3rdparty/mailman/Mailman/versions.pyR <