Menu

#28 Python 3 branch behind

v1.0 (example)
closed-fixed
nobody
None
5
2014-01-30
2013-08-10
No

I notice that there's an 0.6.3 tagged (but not released to PyPI). I also notice that the Python 3 branch has not been kept up-to-date with recent developments. It'd be nice if the Python 3 code weren't in a separate branch to erode. With newer techniques and deprecating older Python versions, it may be fairly straightforward to allow comtypes to run under Python 2 and 3 on a single code base.

I invite your thoughts on the matter.

Discussion

  • Jason R. Coombs

    Jason R. Coombs - 2014-01-17

    I see now that that code was also committed to the trunk, so the Python 3 branch has no novel content relative to the trunk and should just be removed/closed.

     
  • wiggin15

    wiggin15 - 2014-01-29

    Hi Jason, it looks like you fixed this yourself. This ticket can be closed ;)

     
  • Jason R. Coombs

    Jason R. Coombs - 2014-01-30
    • status: open --> closed-fixed
     
  • Jason R. Coombs

    Jason R. Coombs - 2014-01-30

    Yep. Lots to do. Thanks.

     

Log in to post a comment.

MongoDB Logo MongoDB