Changes between Version 16 and Version 17 of GSoC/2018/FullSupportPython3


Ignore:
Timestamp:
Jul 1, 2018, 12:08:18 PM (6 years ago)
Author:
sanjeet
Comment:

Week 7 report added

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2018/FullSupportPython3

    v16 v17  
    336336  Not at the moment.
    337337
     338=== Week 7 ===
     339'''What did I complete this week?'''\\
     340- Updated ctypes to deal with bytes(https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/grass_trunk/lib-python-ctypes/patch_ctypes_changes_from_fork.diff)
     341- Worked on 'temporal' library(https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/grass_trunk/lib-python-temporal/patch_temporal.diff), lot of errors were encountered
     342- Looked into issues for 'pygrass' testsuites which were failing too
     343- Created a spreadsheet(https://docs.google.com/spreadsheets/d/1eAIJtegNWSbBscFChhQzMTl0vmbGPjmrW_013hSw9bI/edit#gid=408919374) detailing errors and information regarding the temporal testsuites
     344- Also, updated the pygrass testsuite details on spreadsheet(https://docs.google.com/spreadsheets/d/1eAIJtegNWSbBscFChhQzMTl0vmbGPjmrW_013hSw9bI/edit#gid=587128881)
     345
     346'''What am I going to achieve for the next week?'''\\
     347- Start exploring GUI library, starting with mapdisp and imgr
     348- Continue working on fixing ctypes module
     349- Continue working on 'temporal' library
     350
     351'''Is there any blocking issue?'''\\
     352  Ctypes are not fully compatible with the Python3 even if they are compiling without any issues. Discussed witb mentors about the next steps and how to deal with ctypes.
     353  Will discuss more about the upcoming milestones and how ctypes handling is to be done so as not to interfare too much with the pending work.
     354