Snidhi Sofpro added the comment:
Hello Tim Peters,
Like you pointed out:
(1) The test code clearly has a mistake.
(2) With the mistake corrected, difflib.SequenceMatcher.get_matching_blocks()
returns results as expected for the given test data.
I'm unable to readily recreate the
New submission from Snidhi Sofpro :
-- Demo case with unexpected results starting from matching block 3
(result of code that follows):
sys.version_info(major=3, minor=6, micro=9, releaselevel='final', serial=0)
Matches between:
http://local:56067/register/2009301621357
New submission from Snidhi Sofpro :
With: Python 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 17:54:52) [MSC v.1900 32 bit
(Intel)] on win32
import datetime;
d_Time = datetime.datetime.strptime('03:30 PM', '%I:%M %p');
d_Time = d_Time.astimezone(datetime.timezone.utc);
# RESULTS I
Snidhi Sofpro added the comment:
Hi team,
Looks like this issue remains per code below:
import multiprocessing, sys, time, traceback;
if __name__ == '__main__':
print(sys.version);
mpd = multiprocessing.Manager().dict();
mpd['prcss'] = {'q'
