✘✘ GRAYBYTE WORDPRESS FILE MANAGER ✘✘

3

� fE6�@s�dZd
dl
Z
d
dlZd
dlZd
dlZd
add�Zdd�ZdZdd	�Z	d
d�Z
dd
�Zdd�ZGdd�d�Z
dd�Zdd�Zedkr�e
je��

dS)afixdiv - tool to fix division operators.

To use this tool, first run `python -Qwarnall yourscript.py 2>warnings'.
This runs the script `yourscript.py' while writing warning messages
about all uses of the classic division operator to the file
`warnings'.  The warnings look like this:

  <file>:<line>: DeprecationWarning: classic <type> division

The warnings are written to stderr, so you must use `2>' for the I/O
redirect.  I know of no way to redirect stderr on Windows in a DOS
box, so you will have to modify the script to set sys.stderr to some
kind of log file if you want to do this on Windows.

The warnings are not limited to the script; modules imported by the
script may also trigger warnings.  In fact a useful technique is to
write a test script specifically intended to exercise all code in a
particular module or set of modules.

Then run `python fixdiv.py warnings'.  This first reads the warnings,
looking for classic division warnings, and sorts them by file name and
line number.  Then, for each file that received at least one warning,
it parses the file and tries to match the warnings up to the division
operators found in the source code.  If it is successful, it writes
its findings to stdout, preceded by a line of dashes and a line of the
form:

  Index: <file>

If the only findings found are suggestions to change a / operator into
a // operator, the output is acceptable input for the Unix 'patch'
program.

Here are the possible messages on stdout (N stands for a line number):

- A plain-diff-style change ('NcN', a line marked by '<', a line
  containing '---', and a line marked by '>'):

  A / operator was found that should be changed to //.  This is the
  recommendation when only int and/or long arguments were seen.

- 'True division / operator at line N' and a line marked by '=':

  A / operator was found that can remain unchanged.  This is the
  recommendation when only float and/or complex arguments were seen.

- 'Ambiguous / operator (..., ...) at line N', line marked by '?':

  A / operator was found for which int or long as well as float or
  complex arguments were seen.  This is highly unlikely; if it occurs,
  you may have to restructure the code to keep the classic semantics,
  or maybe you don't care about the classic semantics.

- 'No conclusive evidence on line N', line marked by '*':

  A / operator was found for which no warnings were seen.  This could
  be code that was never executed, or code that was only executed
  with user-defined objects as arguments.  You will have to
  investigate further.  Note that // can be overloaded separately from
  /, using __floordiv__.  True division can also be separately
  overloaded, using __truediv__.  Classic division should be the same
  as either of those.  (XXX should I add a warning for division on
  user-defined objects, to disambiguate this case from code that was
  never executed?)

- 'Phantom ... warnings for line N', line marked by '*':

  A warning was seen for a line not containing a / operator.  The most
  likely cause is a warning about code executed by 'exec' or eval()
  (see note below), or an indirect invocation of the / operator, for
  example via the div() function in the operator module.  It could
  also be caused by a change to the file between the time the test
  script was run to collect warnings and the time fixdiv was run.

- 'More than one / operator in line N'; or
  'More than one / operator per statement in lines N-N':

  The scanner found more than one / operator on a single line, or in a
  statement split across multiple lines.  Because the warnings
  framework doesn't (and can't) show the offset within the line, and
  the code generator doesn't always give the correct line number for
  operations in a multi-line statement, we can't be sure whether all
  operators in the statement were executed.  To be on the safe side,
  by default a warning is issued about this case.  In practice, these
  cases are usually safe, and the -m option suppresses these warning.

- 'Can't find the / operator in line N', line marked by '*':

  This really shouldn't happen.  It means that the tokenize module
  reported a '/' operator but the line it returns didn't contain a '/'
  character at the indicated position.

- 'Bad warning for line N: XYZ', line marked by '*':

  This really shouldn't happen.  It means that a 'classic XYZ
  division' warning was read with XYZ being something other than
  'int', 'long', 'float', or 'complex'.

Notes:

- The augmented assignment operator /= is handled the same way as the
  / operator.

- This tool never looks at the // operator; no warnings are ever
  generated for use of this operator.

- This tool never looks at the / operator when a future division
  statement is in effect; no warnings are generated in this case, and
  because the tool only looks at files for which at least one classic
  division warning was seen, it will never look at files containing a
  future division statement.

- Warnings may be issued for code not read from a file, but executed
  using the exec() or eval() functions.  These may have
  <string> in the filename position, in which case the fixdiv script
  will attempt and fail to open a file named '<string>' and issue a
  warning about this failure; or these may be reported as 'Phantom'
  warnings (see above).  You're on your own to deal with these.  You
  could make all recommended changes and add a future division
  statement to all affected files, and then re-run the test script; it
  should not issue any warnings.  If there are any, and you have a
  hard time tracking down where they are generated, you can use the
  -Werror option to force an error instead of a first warning,
  generating a traceback.

- The tool should be run from the same directory as that from which
  the original script was run, otherwise it won't be able to open
  files given by relative pathnames.
�Nc
Cs
ytjt
jd
d�d�\}}
Wn*tjk
rH
}
zt|�

dSd}~XnXx0|D](\}}|dkrltt�

dS|dkrPd
aqPW|
s�td�

dS|
d
d�r�t
jj	dt
jd�
t
|
d�
}|dkr�d
St|j��
}|s�td	|
d�
dS|j
�
d}x&|D]}t|||�}	|�
p|	}�q�W|S)
N�
Zhm�z-hz-mz&at least one file argument is requiredz!%s: extra file arguments ignored
r
z&No classic division warnings read from)�getopt�sys�argv�error�usage�print�__doc__�multi_ok�stderr�write�readwarnings�list�keys�sort�process)
Zopts�args�msg�
o�
a�warnings�files�exit�filename�
x�r�9/opt/alt/python36/lib64/python3.6/Tools/scripts/fixdiv.py�main�s:




























rc

CsJtj
jd
tjd|f�

tj
jdtjd�

tj
jdtjd�

dS)Nz%s: %s
r
zUsage: %s [-m] warnings
z"Try `%s -h' for more information.
)rrr
r)
rrrrr�s


rzL^(.+?):(\d+): DeprecationWarning: classic (int|long|float|complex) division$c
Cs�tj
t�
}
yt|�
}Wn0tk
rF
}
ztjjd
|�

dSd}~XnXi}x�|j�}|s\P|
j	|�
}|s�|j
d�
dkrNtjjd|�

qN|j�\}}}	|j|�
}
|
dkr�g||<}
|
j
t|�
tj|	�
f�

qNW|j�
|S)Nzcan't open: %s
Zdivisionr
zWarning: ignored input )�re�compile�PATTERN�open�IOErrorrrr
�readline�match�find�groups�get�append�int�intern�close)Zwarningsfile�prog�
frr�line�
mr�lineno�whatrrrrr�s.

























rcCs�td
d�

yt
|�
}Wn0tk
rH
}
ztjjd|�

dSd}~XnXtd|�
t|�
}|
j�
d}tj	|j
�
}�xt|�
\}}}	}
|dkr�Pg}x6|t|
�
kr�|
|d|kr�|j
|
|�

|d7}q�W|r�t||�
g}x:|t|
�
k�
r|
|d|k
�
r|j
|
|�

|d7}q�W|	�
r0|�
r0qx|	�
rJ|�
rJt|	d�
qx|�
rd|	�
rdt||�
qxt|	�
dk�
r�t�
s�g}
d}x2|	D]*\\}}}||k�
r��
q�|
j
|�

|}�
q�Wt|
�
dk�
r�td|
d�
n$td	d
d�
td|
d|
df�

g}g}g}xH|D]@\}}|dk�r&|j
|�

n |d k�r<|j
|�

n
|j
|�

�qWd}�
x0|	D�
]&\\}}}||k�rt�qX|}t|�
}|||d�dk�r�td|�

td|�
�qX|�r�td||�
td|�
n�|�r$|�r$td||f�

td|�
td�

td|d|�d||d��
nZ|�rJ|�rJtd|�

td|�
n4|�rX|�rXtddj|�
dj|�
|f�

td|�
�qXWqxW|j�
dS)!N�
-�Fzcan't open: %s
rzIndex:r
zNo conclusive evidencez$*** More than one / operator in linez**** More than one / operator per statement�
 )
�endzin lines %d-%dr*�long�float�complex�
/z)*** Can't find the / operator in line %d:�
*z*** Bad warning for line %d:z%dc%d�
<z---�
>z$True division / operator at line %d:�
=z-*** Ambiguous / operator (%s, %s) at line %d:�
|�
?���)r*r7)r8r9)r	r"r#rrr
�FileContextr�tokenize�generate_tokensr$�scanline�lenr)�reportphantomwarnings�reportr�chop�joinr,)rr�fprr.�index�
g�startlineno�	endlineno�slashesZlineinfoZorphansrZrows�lastrow�row�colr/ZintlongZfloatcomplexZbadr1r2rrrr�s�






















"



















































$







rc	Cs�g}d}d}x2|D]*\}}||kr2|g
}|j|�

|j|�

qWxD|D]<}|d
}dj
|dd��
}td||f�

|
j|dd�
qFWdS)Nr
r:rz$*** Phantom %s warnings for line %d:r;)
�mark)r)rJr	rH)	rr.ZblocksrQZ	lastblockrRr2�blockZwhatsrrrrG$
s














rGcCsHd}x>|D]6\\}}}||kr
td
|
|f�

tdt
|�
�
|}q
WdS)Nz*** %s on line %d:r;)r	rI)rP�messagerQrRrSr/rrrrH3
s





rHc@s8eZ
dZddd�
Zdd�Zdd�Zd	d
�Zdd
d�
ZdS)rB�rcCs(|
|_d
|_
d|_d|_g|_g|_dS)NrWrr
)rK�windowr1�eoflookahead�	lookahead�buffer)�selfrKrXr1rrr�__init__<
s





zFileContext.__init__c
CsDx>t|j
�
|jkr>|jr>|jj�}
|
s0d
|_P|j
j|
�

qWdS)Nr)rFrZrXrYrKr$r))r\r/rrr�fillC
s






zFileContext.fillc
Cs<|j�
|j
sd
S|j
jd�
}
|jj|
�

|jd7_|
S)N�r
r)r^rZ�popr[r)r1)r\r/rrrr$J
s






zFileContext.readlinecCs�|j�
|j
t|j�
}|j
t|j�
}||
k
o<|j
kn
rP|j|
|S|j
|
k
od|kn
rz|j|
|j
St�
dS)
N)r^r1rFr[rZ�KeyError)r\rLZbufstartZlookendrrr�__getitem__R
s







zFileContext.__getitem__Nr;c
Cs\|dkr|
}xJt|
|d
�D]8}y||
}Wnt
k
rD


d}YnXt|t|�
�
qWdS)Nrz<missing line>)�rangerar	rI)r\�firstZlastrT�
ir/rrrrH[
s








zFileContext.report)rWr)Nr;)�__name__�
__module__�__qualname__r]r^r$rbrHrrrrrB;
s


	rBc
	Csdg}
d}d}xL|D]D\}}}}}|d
}|dkr4|}|dkrJ|
j||f�

|t
jkrPqW|||
fS)Nr
r:�/=)r:ri)r)rC�NEWLINE)	rMrPrNrO�type�token�startr6r/rrrrEe
s












rEc

Cs|jd
�
r|dd�S|SdS)N�

rrA)
�endswith)
r/rrrrIs
s


rI�__main__)r
rrrrCrrrr!rrrGrHrBrErIrfrrrrr�<module>�s"


 W*