-=[ Mr. Bumblebee ]=-
_Indonesia_

Path : /usr/lib/python2.7/dist-packages/bzrlib/
File Upload :
Current File : //usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyc

ó
ÜdPc@@sndZddlmZddlZddlZddlmZmZmZm	Z	m
Z
mZmZddl
mZddlmZmZmZmZmZmZmZmZmZmZmZmZddlmZmZddlm Z m!Z!m"Z"dd	l#m$Z$dd
l%m&Z&e&e'ƒdƒdZ(d
Z)de	j*fd„ƒYZ+de,fd„ƒYZ-d„Z.dS(s‚On-disk mutex protecting a resource

bzr on-disk objects are locked by the existence of a directory with a
particular name within the control directory.  We use this rather than OS
internal locks (such as flock etc) because they can be seen across all
transports, including http.

Objects can be read if there is only physical read access; therefore
readers can never be required to create a lock, though they will
check whether a writer is using the lock.  Writers can't detect
whether anyone else is reading from the resource as they write.
This works because of ordering constraints that make sure readers
see a consistent view of existing data.

Waiting for a lock must be done by polling; this can be aborted after
a timeout.

Locks must always be explicitly released, typically from a try/finally
block -- they are not released from a finalizer or when Python
exits.

Locks may fail to be released if the process is abruptly terminated
(machine stop, SIGKILL) or if a remote transport becomes permanently
disconnected.  There is therefore a method to break an existing lock.
This should rarely be used, and generally only with user approval.
Locks contain some information on when the lock was taken and by who
which may guide in deciding whether it can safely be broken.  (This is
similar to the messages displayed by emacs and vim.) Note that if the
lock holder is still alive they will get no notification that the lock
has been broken and will continue their work -- so it is important to be
sure they are actually dead.

A lock is represented on disk by a directory of a particular name,
containing an information file.  Taking a lock is done by renaming a
temporary directory into place.  We use temporary directories because
for all known transports and filesystems we believe that exactly one
attempt to claim the lock will succeed and the others will fail.  (Files
won't do because some filesystems or transports only have
rename-and-overwrite, making it hard to tell who won.)

The desired characteristics are:

* Locks are not reentrant.  (That is, a client that tries to take a
  lock it already holds may deadlock or fail.)
* Stale locks can be guessed at by a heuristic
* Lost locks can be broken by any client
* Failed lock operations leave little or no mess
* Deadlocks are avoided by having a timeout always in use, clients
  desiring indefinite waits can retry or set a silly big timeout.

Storage formats use the locks, and also need to consider concurrency
issues underneath the lock.  A format may choose not to use a lock
at all for some operations.

LockDirs always operate over a Transport.  The transport may be readonly, in
which case the lock can be queried but not acquired.

Locks are identified by a path name, relative to a base transport.

Calling code will typically want to make sure there is exactly one LockDir
object per actual lock on disk.  This module does nothing to prevent aliasing
and deadlocks will likely occur if the locks are aliased.

In the future we may add a "freshen" method which can be called
by a lock holder to check that their lock has not been broken, and to
update the timestamp within it.

Example usage:

>>> from bzrlib.transport.memory import MemoryTransport
>>> # typically will be obtained from a BzrDir, Branch, etc
>>> t = MemoryTransport()
>>> l = LockDir(t, 'sample-lock')
>>> l.create()
>>> token = l.wait_lock()
>>> # do something here
>>> l.unlock()

Some classes of stale locks can be predicted by checking: the host name is the
same as the local host name; the user name is the same as the local user; the
process id no longer exists.  The check on user name is not strictly necessary
but helps protect against colliding host names.
i(tabsolute_importN(tconfigtdebugterrorstlocktosutilstuiturlutils(tonly_raises(tDirectoryNotEmptyt
FileExiststLockBreakMismatcht
LockBrokentLockContentiontLockCorruptt
LockFailedtLockNotHeldt
NoSuchFilet	PathErrortResourceBusytTransportError(tmuttertnote(tformat_deltat
rand_charst
get_host_name(tgettext(tlazy_imports
from bzrlib import rio
igð?tLockDircB@s4eZdZdZdddd„Zd„Zed„ƒZdd„Z	d„Z
d	„Zd
„Zd„Z
eeeƒd„ƒZd
„Zd„Zd„Zd„Zd„Zd„Zd„Zd„Zd„Zd„Zdddd„Zd„Zd„Zdd„Zd„Z d„Z!d„Z"d„Z#RS( s(Write-lock guarding access to data.
    s/infoi¤iícC@s~||_||_t|_t|_t|_|d|_|j|j|_||_	||_
t|_||_
d|_dS(sºCreate a new LockDir object.

        The LockDir is initially unlocked - this just creates the object.

        :param transport: Transport which will contain the lock

        :param path: Path to the lock within the base directory of the
            transport.

        :param extra_holder_info: If passed, {str:str} dict of extra or
            updated information to insert into the info file when the lock is
            taken.
        s/heldN(t	transporttpathtFalset
_lock_heldt_locked_via_tokent_fake_read_lockt	_held_dirt_LockDir__INFO_NAMEt_held_info_patht_file_modebitst
_dir_modebitsRt_report_functiontextra_holder_infotNonet_warned_about_lock_holder(tselfRRt
file_modebitstdir_modebitsR)((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt__init__­s					
				cC@s d|jj|jj|jfS(Ns%s(%s%s)(t	__class__t__name__RtbaseR(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt__repr__És	cC@s|jS(N(R (R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt<lambda>ÎscC@sY|jdƒy|jj|jd|ƒWn(ttfk
rT}t||ƒ‚nXdS(s¾Create the on-disk lock.

        This is typically only called when the object/directory containing the
        directory is first created.  The lock is not held when it's created.
        screate lock directorytmodeN(t_traceRtmkdirRRRR(R,R5te((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytcreateÐs

c	C@sÝ|jdƒtjƒ}y|jƒ}Wn;tjtfk
rf}|jd|ƒt||ƒ‚nXx×tr@y|jj	||j
ƒPWqjtjtttt
fk
r
}|jd|ƒ|jƒ}|jd|ƒy|j|ƒWq=|j|ƒ‚q=Xqjtk
r<}|jd|ƒ|j|ƒ‚qjXqjW|jƒ}|jd|ƒ|dkr{t|dƒ‚n|jdƒ|jkr¯|jd	ƒt|ƒ‚nt|_|jd
tjƒ|dƒ|jS(
s6Make the pending directory and attempt to rename into place.

        If the rename succeeds, we read back the info file to check that we
        really got the lock.

        If we fail to acquire the lock, this method is responsible for
        cleaning up the pending directory if possible.  (But it doesn't do
        that yet.)

        :returns: The nonce of the lock, if it was successfully acquired.

        :raises LockContention: If the lock is held by someone else.  The
            exception contains the info of the current holder of the lock.
        s
lock_write...s$... failed to create pending dir, %ss... contention, %ssother holder is %rs... lock failed, %ssafter locking, info=%rs0lock was renamed into place, but now is missing!tnonces8rename succeeded, but lock is still held by someone elses... lock succeeded after %dmsièN(R6ttimet_create_pending_dirRRRRtTrueRtrenameR#R	R
Rtpeekt_handle_lock_contentiont_remove_pending_dirt	ExceptionR*tgetR:R
R (R,t
start_timettmpnameR8tother_holdertinfo((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt
_attempt_lockÜsH
	




		cC@s˜|dk	rˆ|jƒrˆ|jƒjdƒr…tjjddtj|j	j
|jƒdt|ƒƒ|j
|ƒ|jdƒdSqˆnt|ƒ‚dS(sóA lock we want to take is held by someone else.

        This function can: tell the user about it; possibly detect that it's
        safe or appropriate to steal the lock, or just raise an exception.

        If this function returns (without raising an exception) the lock will
        be attempted again.

        :param other_holder: A LockHeldInfo for the current holder; note that
            it might be None if the lock can be seen to be held but the info
            can't be read.
        slocks.steal_deadtlocks_steal_deadtlock_urltother_holder_infosstole lock from dead holderN(R*tis_lock_holder_known_deadt
get_configRCRt
ui_factorytshow_user_warningRtjoinRR2Rtunicodetforce_breakR6R
(R,RF((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR@s
	



cC@sh|jd|ƒy+|jj||jƒ|jj|ƒWn&tk
rc}ttdƒ|ƒnXdS(sŸRemove the pending directory

        This is called if we failed to rename into place, so that the pending
        dirs don't clutter up the lockdir.
        s	remove %sserror removing pending lock: %sN(R6RtdeleteR$trmdirRRR(R,RER8((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRA6scC@s¹d|jtdƒf}y|jj|ƒWnAtk
rp|jdƒ|jd|jƒ|jj|ƒnXtj	|j
ƒ}|jdƒ|_|jj
||j|jƒƒ|S(Ns	%s/%s.tmpi
s*lock directory does not exist, creating itR5R:(RRRR7RR6R9R'tLockHeldInfotfor_this_processR)RCR:tput_bytes_non_atomicR$tto_bytes(R,RERG((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR<Cs


cC@st|jrt|_dS|js,tj|ƒS|jrJt|_t|_n&|j}tjƒ}|jdƒd|j	t
dƒf}|jƒ|jj
|j|ƒt|_|jj||jƒy|jj|ƒWn3tk
r}|jd|ƒ|jj|ƒnX|jdtjƒ|dƒtj|jj|j	ƒ|ƒ}x|jdD]}||ƒq\WdS(	sRelease a held lock
        Nt	unlockings%s/releasing.%s.tmpis2doing recursive deletion of non-empty directory %ss... unlock succeeded after %dmsièt
lock_released(R"RR Rtcant_unlock_not_heldR!R:R;R6RRtconfirmRR>R#RSR$RTR	tdelete_treet
LockResulttabspaththooks(R,t	old_nonceRDRER8tresultthook((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytunlockYs8			
			

				cC@sÀ|jƒy|jƒ}Wn@tk
r\}tjjd|fƒrX|j|jƒndSX|dk	r¼tjj	ddt
dt|ƒƒƒr¼|j|ƒ}tjj
d|jƒq¼ndS(s\Break a lock not held by this instance of LockDir.

        This is a UI centric function: it uses the ui.ui_factory to
        prompt for input if a lock is detected and there is any doubt about
        it possibly being still active.  force_break is the non-interactive
        version.

        :returns: LockResult for the broken lock.
        uBreak (corrupt %r)NuBreak %(lock_info)ssbzrlib.lockdir.breakt	lock_infos
Broke lock %s(t_check_not_lockedR?RRRNtget_booleantforce_break_corruptt	file_dataR*tconfirm_actiontdictRQRRtshow_messageRJ(R,tholder_infoR8Rb((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt
break_lock…s

		cC@sEt|tƒs"td|ƒ‚n|jƒ|jƒ}|dkrHdS||krit|||ƒ‚nd|jtdƒf}|j	j
|j|ƒ||j}|j
|ƒ}||krÕt|||ƒ‚n|j	j|ƒ|j	j|ƒtj|j	j|jƒ|jdƒƒ}x|jdD]}||ƒq-W|S(s2Release a lock held by another process.

        WARNING: This should only be used when the other process is dead; if
        it still thinks it has the lock there will be two concurrent writers.
        In general the user's approval should be sought for lock breaks.

        After the lock is broken it will not be held by any process.
        It is possible that another process may sneak in and take the
        lock before the breaking process acquires it.

        :param dead_holder_info:
            Must be the result of a previous LockDir.peek() call; this is used
            to check that it's still held by the same process that the user
            decided was dead.  If this is not the current holder,
            LockBreakMismatch is raised.

        :returns: LockResult for the broken lock.
        sdead_holder_info: %rNs%s/broken.%s.tmpiR:tlock_broken(t
isinstanceRUt
ValueErrorRfR?R*RRRRR>R#R$t_read_info_fileRSRTRR^R_RCR`(R,tdead_holder_infotcurrent_infoREtbroken_info_pathtbroken_infoRbRc((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRR s*

cC@sì|jƒd|jtdƒf}|jj|j|ƒ||j}|jj|ƒ}tj	|ƒ}||krˆt
|||ƒ‚n|jj|ƒ|jj|ƒt
j|jj|jƒƒ}x|jdD]}||ƒqÔWdS(ssRelease a lock that has been corrupted.

        This is very similar to force_break, it except it doesn't assume that
        self.peek() can work.

        :param corrupt_info_lines: the lines of the corrupted info file, used
            to check that the lock hasn't changed between reading the (corrupt)
            info file and calling force_break_corrupt.
        s%s/broken.%s.tmpiRoN(RfRRRR>R#R$t	get_bytesRtsplit_linesRRSRTRR^R_R`(R,tcorrupt_info_linesRERutbroken_contenttbroken_linesRbRc((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRhÍs

cC@s |jrtd|ƒ‚ndS(s5If the lock is held by this instance, raise an error.scan't break own lock: %rN(R tAssertionError(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRfês	cC@sj|jst|ƒ‚n|jƒ}|dkr?t|ƒ‚n|jdƒ|jkrft|ƒ‚ndS(s\Make sure that the lock is still held by this locker.

        This should only fail if the lock was broken by user intervention,
        or if the lock has been affected by a bug.

        If the lock is not thought to be held, raises LockNotHeld.  If
        the lock is thought to be held but has been broken, raises
        LockBroken.
        R:N(R RR?R*RRCR:(R,RG((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR\ïs
	cC@stj|jj|ƒƒS(sbRead one given info file.

        peek() reads the info file of the lock holder, if any.
        (RUtfrom_info_file_bytesRRw(R,R((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRrscC@sNy'|j|jƒ}|jdƒ|SWn tk
rI}|jdƒnXdS(sÛCheck if the lock is held by anyone.

        If it is held, this returns the lock info structure as a dict
        which contains some information about the current lock holder.
        Otherwise returns None.
        speek -> heldspeek -> not heldN(RrR%R6R(R,RGR8((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR?s
cC@sdS(sDWrite information about a pending lock to a temporary file.
        N((R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt
_prepare_infoscC@sn|jrt|ƒ‚n|jƒ}tj|jj|jƒ|jƒ}x|j	dD]}||ƒqVW|S(sùTake the lock; fail if it's already held.

        If you wish to block until the lock can be obtained, call wait_lock()
        instead.

        :return: The lock token.
        :raises LockContention: if the lock is held by someone else.
        t
lock_acquired(
R"R
RHRR^RR_RR:R`(R,Rbthook_resultRc((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytattempt_locks		cC@sD|jj|jƒ}|jdƒr:|jdƒd}nd}|S(s?Give a nicely-printable representation of the URL of this lock.sfile://s.bzr/it(RR_Rt
startswithtsplit(R,RJ((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytlock_url_for_display/s
cC@sÿ|dkrt}n|dkr*t}ntjƒ|}d}d}d}|jƒ}x trú|d7}y|jƒSWntk
rŒnX|jƒ}	|	dk	rn|	|krn|dkrÌt	dƒ}
nt	dƒ}
|	}t	dƒj
|
||	ƒ}|dkr#tjdtj|ƒƒ}n|dkrJ|dt	dƒ|7}n|dt	d	ƒ7}|j
|ƒn|dk	r¢||kr¢|jd
ƒt|ƒ‚ntjƒ||krØ|jd|ƒtj|ƒq[|jd|ƒtd
|ƒ‚q[WdS(s}Wait a certain period for a lock.

        If the lock can be acquired within the bounded time, it
        is taken and this returns.  Otherwise, LockContention
        is raised.  Either way, this function should return within
        approximately `timeout` seconds.  (It may be a bit more if
        a transport operation takes a long time to complete.)

        :param timeout: Approximate maximum amount of time to wait for the
        lock, in seconds.

        :param poll: Delay in seconds between retrying the lock.

        :param max_attempts: Maximum number of times to try to lock.

        :return: The lock token.
        iisUnable to obtainsLock owner changed fors{0} lock {1} {2}.s%H:%M:%Ss
s7Will continue to try until %s, unless you press Ctrl-C.s#See "bzr help break-lock" for more.sexceeded %d attemptsswaiting %ssstimeout after waiting %sss(local)N(R*t_DEFAULT_TIMEOUT_SECONDSt_DEFAULT_POLL_SECONDSR;R…R=RR
R?Rtformattstrftimet	localtimeR(R6tsleep(R,ttimeouttpolltmax_attemptstdeadlinetdeadline_strt	last_infot
attempt_countRJtnew_infotstarttmsg((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt	wait_lock:sP			

			
cC@s
t|_dS(N(R=R!(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytleave_in_place„scC@s
t|_dS(N(RR!(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytdont_leave_in_place‡scC@sF|dk	r8|j|ƒ||_t|_t|_|S|jƒSdS(sÙWait for and acquire the lock.

        :param token: if this is already locked, then lock_write will fail
            unless the token matches the existing lock.
        :returns: a token if this instance supports tokens, otherwise None.
        :raises TokenLockingNotSupported: when a token is given but this
            instance doesn't support using token locks.
        :raises MismatchedToken: if the specified token doesn't match the token
            of the existing lock.

        A token should be passed in if you know that you have locked the object
        some other way, and need to synchronise this object's state with that
        fact.

        XXX: docstring duplicated from LockableFiles.lock_write.
        N(R*tvalidate_tokenR:R=R R!R–(R,ttoken((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt
lock_writeŠs
			cC@s.|js|jr!t|ƒ‚nt|_dS(s¯Compatibility-mode shared lock.

        LockDir doesn't support shared read-only locks, so this
        just pretends that the lock is taken but really does nothing.
        N(R R"R
R=(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt	lock_read¤scC@st|dk	rp|jƒ}|dkr-d}n|jdƒ}||kr]tj||ƒ‚qp|jd|ƒndS(NR:srevalidated by token %r(R*R?RCRt
TokenMismatchR6(R,RšRGt
lock_token((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR™³s	cG@s3dtjkrdStt|ƒd||ƒdS(NRs: (Rtdebug_flagsRtstr(R,Rˆtargs((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR6ÀscC@s
tjƒS(s0Get the configuration that governs this lockdir.(RtGlobalStack(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRMÅsN($R1t
__module__t__doc__R$R*R/R3tpropertytis_heldR9RHR@RAR<RRRRdRnRRRhRfR\RrR?R~RR…R–R—R˜R›RœR™R6RM(((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR§s<		A		
	,		-								J				
	RUcB@s}eZdZd„Zd„Zd„Zd„Zd„Zed„ƒZ	d„Z
ed„ƒZd	„Zd
„Z
d„ZRS(s‚The information recorded about a held lock.

    This information is recorded into the lock when it's taken, and it can be
    read back by any process with access to the lockdir.  It can be used, for
    example, to tell the user who holds the lock, or to try to detect whether
    the lock holder is still alive.

    Prior to bzr 2.4 a simple dict was used instead of an object.
    cC@s
||_dS(N(t	info_dict(R,R§((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR/ØscC@sd|jj|jfS(s1Return a debugging representation of this object.s%s(%r)(R0R1R§(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR3ÛscC@s|jƒ}tdƒ|S(s2Return a user-oriented description of this object.uJheld by %(user)s on %(hostname)s (process #%(pid)s), acquired %(time_ago)s(tto_readable_dictR(R,td((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt__unicode__ßsc	C@s¨|jjdƒ}|dkr'd}n#ttjƒt|jdƒƒ}|jjddƒ}|jjddƒ}|jjddƒ}td|d|d|d|ƒS(	s#Turn the holder info into a dict of human-readable attributes.

        For example, the start time is presented relative to the current time,
        rather than as seconds since the epoch.

        Returns a list of [user, hostname, pid, time_ago] all as readable
        strings.
        RDs	(unknown)tusers	<unknown>thostnametpidttime_agoN(R§RCR*RR;tintRk(R,RDR®R«R¬R­((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR¨æs		 cC@s|jj|ƒS(s;Return the contents of a field from the lock info, or None.(R§RC(R,t
field_name((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRCþscC@swtdtƒdttjƒƒdtdƒdtttjƒƒƒdtƒƒ}|dk	rm|j
|ƒn||ƒS(sDReturn a new LockHeldInfo for a lock taken by this process.
        R¬R­R:iRDR«N(RkRR tostgetpidRR¯R;tget_username_for_lock_infoR*tupdate(tclsR)RG((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRVs	cC@stj|j}|jƒS(N(triotStanzaR§t	to_string(R,ts((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRXscC@sˆtj|ƒ}ytj|ƒ}Wn9tk
r]}td|ƒtdt|ƒ|ƒ‚nX|dkrt|iƒS||j	ƒƒSdS(s-Construct from the contents of the held file.sCorrupt lock info file: %rs could not parse lock info file: N(
RRxR¶tread_stanzaRqRRR R*tas_dict(Rµtinfo_file_bytestlineststanzaR8((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR}s


cC@s.tt|ƒt|ƒƒp-t|j|jƒS(s!Value comparison of lock holders.(tcmpttypeR§(R,tother((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt__cmp__'scC@sO|jdƒtƒkoN|jdƒttjƒƒkoN|jdƒtƒkS(s9True if this process seems to be the current lock holder.R¬R­R«(RCRR R±R²R³(R,((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pytis_locked_by_this_process-s!cC@sÇ|jdƒtƒkrtS|jdƒdkr5tS|jdƒtƒkrQtS|jjddƒ}|std|fƒtSyt|ƒ}Wn&tk
r¹td||fƒtSXt	j
|ƒS(sTrue if the lock holder process is known to be dead.

        False if it's either known to be still alive, or if we just can't tell.

        We can be fairly sure the lock holder is dead if it declared the same
        hostname and there is no process with the given pid alive.  If people
        have multiple machines with the same hostname this may cause trouble.

        This doesn't check whether the lock holder is in fact the same process
        calling this method.  (In that case it will return true.)
        R¬t	localhostR«R­sno pid recorded in %rscan't parse pid %r from %rN(RCRRR³R§R*RR¯RqRtis_local_pid_dead(R,tpid_strR­((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRL4s"
(R1R£R¤R/R3RªR¨RCtclassmethodRVRXR}RÂRÃRL(((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyRUÍs									cC@s9ytjƒjdƒSWntjk
r4tjƒSXdS(sªGet a username suitable for putting into a lock.

    It's ok if what's written here is not a proper email address as long
    as it gives some clue who the user is.
    temailN(RR¢RCRtNoWhoamiRtgetuser_unicode(((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyR³Vs(/R¤t
__future__RR±R;tbzrlibRRRRRRRtbzrlib.decoratorsRt
bzrlib.errorsR	R
RRR
RRRRRRRtbzrlib.traceRRtbzrlib.osutilsRRRtbzrlib.i18nRtbzrlib.lazy_importRtglobalsR†R‡tLockRtobjectRUR³(((s2/usr/lib/python2.7/dist-packages/bzrlib/lockdir.pyt<module>cs&4	R	ÿÿ(‰

Copyright © 2017 || Recoded By Mr.Bumblebee