Monthly report: July / August 2020

Posted on Tue 01 September 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #26. You'll find some updates for July / August 2020.

FoFiX

Pull Requests (PR):

  • opened / closed PR: "Fixing issue #208 by moving PATH adjustments earlier" #222
  • opened / closed PR: "Fixing issue #208 on Windows by moving the modification to the PATH e…" #223
  • opened / merged PR …

Continue reading

Monthly report: June 2020

Posted on Wed 01 July 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #25. You'll find some updates for June 2020.

FoFiX

Pull Requests (PR):

  • merged PR: "Use Pillow version number" #185
  • merged PR: "Bump pillow from 4.3.0 to 6.2.0" #210
  • opened / merged PR: "Bump Pillow from 6.2.0 to 6.2.2 …

Continue reading

Monthly report: May 2020

Posted on Mon 01 June 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #24. You'll find some updates for May 2020.

FoFiX

Pull Requests (PR):

  • merged PR: "Tests: init tests for the core.Scene module" #216
  • opened PR: "VideoPlayer: extract the C++ extension" #217

Issues:

  • opened / closed issue: "change python version" #218

Other stats:

  • 297 stars (+7)
  • 76 …

Continue reading

Monthly report: April 2020

Posted on Fri 01 May 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #23. You'll find some updates for April 2020.

FoFiX

Pull Requests (PR):

  • merged PR: "Clean up the GameEngine module" #170
  • merged PR: "Tests: init tests for the game.MainMenu module" #182
  • merged PR: "CMGL: replace the C-extension by pure Python code" #212
  • opened / merged PR …

Continue reading

Monthly report: January / February / March 2020

Posted on Wed 01 April 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #22. You'll find some updates for the first quarter 2020.

The main goal of this first quarter was to put Python C-extensions to their own repo and / or replace them with pure Python code to make a release easier than today.

FoFiX

Pull Requests (PR …


Continue reading

Monthly report: December 2019

Posted on Wed 01 January 2020 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #21. You'll find some updates for December 2019.

FoFiX

Stats:

  • 282 stars (+4)
  • 74 forks
  • 57 issues (6)
  • 11 PR

Fretwork

Issues:


Continue reading

Monthly report: November 2019

Posted on Sun 01 December 2019 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #20. You'll find some updates for November 2019.

Release

After 10 years, I decided to release the v3.122. This release is just the v3.121 with some quick patches. Not a big one, but a useful one :).

FoFiX

Pull Requests (PR):

  • opened PR: "Bump …

Continue reading

Monthly report: October 2019

Posted on Fri 01 November 2019 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #19. You'll find some updates for October 2019.

FoFiX

Pull Requests (PR):

  • merged PR: "Split main game code from launcher" #107
  • opened / merged PR: "Launcher: fix the name of the args variable" #204
  • opened / merged PR: "Compile translations before launching the game" #206

Issues:

  • opened …

Continue reading

Monthly report: August / September 2019

Posted on Tue 01 October 2019 in reports • Tagged with reports, monthly • 1 min read

Here is the monthly report #18. You'll find some updates for August / September 2019.

Blog

New post about Python 3: Moving to Python 3.

FoFiX

Pull Requests (PR):

  • opened / merged PR: "Clean up the Rockmeter module" #202
  • opened / merged PR: "Remove the LinedConfigParser module" #203

Other stats:

  • 267 stars (+11 …

Continue reading

Moving to Python 3

Posted on Sun 15 September 2019 in general • Tagged with general, python3 • 1 min read

Python 3

Python 2 will reach its end of life in 01/01/2020. This means we will need to move our code to Python 3.

This work already began, and an issue was opened #110.

However, this is not an easy task for us to move to Python 3 …


Continue reading