Nuitka Blog - Posts tagged gsoc2019

bksahu’s GSoC warp up

2019-08-25T19:55:00+02:00

Hello everyone!

GSoC 2019 has almost come to an end! It’s the time to wrap up this mega event started back in May 2019. Under the mentorship of Mentor Hayen, my learning experience has undergone a roller-coaster ride and it has not only boosted my growth as a developer but also as an individual. Over the last 3 months the following are my major contributions to this project:

Built-ins Optimizations

“any”: PR #246
- nuitka.nodes.BuiltinAnyNodes node added to optimize the “any” built-in.
- Developed an algorithm to predict the “any” for arguments having repetitive values at compile time. For example:
  
  any([0]*255) -> False
  
  any([False, False, True]) -> True
- Extended support for range, set and dict built-ins.
- Added the optimized C side support too
- Added a method getMetaClassBase to make Python 2 and Python 3 compatible while working with metaclasses.
Issue reported and closed Issue #349
- Created a new module nuitka.nodes.IterationHandles to work with iterables.
- Added support of Iteration for non-mutable types.
“all”: PR #407
- Added nuitka.nodes.BuiltinAllNodes to optimize the “all” built-ins.
- Developed an algorithm similar to “any” to predict the “all” arguments. For example:
  
  all([0, 0, 1]) -> False
  
  all([True]*100) -> True
- Other similar optimizations are done like “any” built-in.
- Additionally, added a new testing module tests.optimizations.CommonOptimizations to test the built-ins optimizations at the same place.
“abs”: PR #419
- Added new operation node ExpressionOperationAbs to optimize the abs built-in.
- Manually added shapeSlotAbs to different shapes.
- Finally pre-computed the compile time constant abs

“max” and “min”: PR #442

This PR is work in progress and is half complete.
This is the first optimizations in which I used reformulations instead of added in a new node.

Pseudo-code of “min” reformulation:

def _min(a, b, c, ...):
 tmp_arg1 = a
 tmp_arg2 = b
 tmp_arg3 = c
 ...
 result = tmp_arg1
 if keyfunc is None: # can be decided during re-formulation
     tmp_key_result = keyfunc(result)
     tmp_key_candidate = keyfunc(tmp_arg2)
     if tmp_key_candidate < tmp_key_result:
         result = tmp_arg2
         tmp_key_result = tmp_key_candidate
     tmp_key_candidate = keyfunc(tmp_arg3)
     if tmp_key_candidate < tmp_key_result:
         result = tmp_arg3
         tmp_key_result = tmp_key_candidate
     ...
 else:
     if tmp_arg2 < result:
         result = tmp_arg2
     if tmp_arg3 < result:
         result = tmp_arg3
     ...
  return result

Adding support for keyfunc is pending

“zip”: PR #462

This built-in uses both types of optimizations that the previous built-ins optimizations used.
zip for Python 2 uses the reformulations.
Pseudo-code of “zip” reformulation:

def _zip(a, b, c, ... ):
# First assign, to preserve order of execution,
# the arguments might be complex expressions.
tmp_arg1 = a
tmp_arg2 = b
tmp_arg3 = c
...
tmp_iter_1 = iter(tmp_arg1)
tmp_iter_2 = iter(tmp_arg2)
tmp_iter_3 = iter(tmp_arg3)
...
# could be more
tmp_result = []
try:
    while 1:
        tmp_result.append(
            (
                 next(tmp_iter_1),
                 next(tmp_iter_2),
                 next(tmp_iter_3),
                 ...
            )
         )
   except StopIteration:
       pass
 return tmp_result

zip for Python 3 needs a new node that calls the zip because unlike zip in Python 2, zip in Python 3 returns a zipobject.

Test suite

Search mode “All”: PR #378

In the test suite, I added a new search mode “all” that will test all the modules and return all the results at once. For example:

$ ./tests/basics/run_all.py all
   Using concrete python 2.7.12 on x86_64
   Comparing output of 'Asserts.py' using '/usr/bin/python' with flags silent, expect_success, remove_output,     recurse_all, original_file, cpython_cache, plugin_enable:pylint-warnings ...
   .
   .
   .
   .
   Total 0 error(s) found.

Search mode “Only”: PR #333

Added “only” search mode to test only a single module. For example:

$ ./tests/basics/run_all.py only BuiltinsTest.py
   Using concrete python 2.7.12 on x86_64
   Skipping Asserts.py
   Skipping Assignments.py
   Skipping BigConstants.py
   Skipping Branching.py
   Skipping BuiltinOverload.py
   Skipping BuiltinSuper.py
   Comparing output of 'BuiltinsTest.py' using '/usr/bin/python' with flags silent, expect_success, remove_output, recurse_all, original_file, cpython_cache, plugin_enable:pylint-warnings ...

Reported and closed Issue #334: PR #336
- Fixed the autoformat bug by reading and writing the files in bytes instead of string.

Documentation

Nuitka git work flow: PR #485

And other minor doc fixes are added with their respective pull requests.

What I learned

Learned the software engineering principles and how to keep my work clean.
I also learned how to effectively use software designing principles like DRY and KISS.
Got exposed to Nuitka internals which helped me to better understand how compilers in general work.
Explored how CPython works internally.
Got some great advice from Mentor Hayen about starting my professional career in Software engineering.

Overall, it was a great experience to be a part of Nuitka :)

Yours,

Batakrishna

Intro

2019-08-23T07:00:00+02:00

As Google Summer of Code (GSoC) is coming to an end, I am writing this blog post as a final summary describing all the work I have done as well as my experiences in this program.

Summary of My Work

#314 run_all.py new special-comment mechanism & Urllib3Using.py
- Before GSoC started, I looked around for whatever work I could help with.
- In this pull request, I added a checkRequirements function for the Nuitka standalone test suite.
- This function checks for special-comments at the top of standalone tests in the format of # nuitka-skip-unless-expression: expression to be evaluated OR # nuitka-skip-unless-imports: module1,module2,... and will decide whether to skip a test depending on if its specified requirements are met.
- In addition, standalone test Urllib3Using.py was created.
- This pull request was soon merged and allowed me the lucky opportunity of GSoC 2019 with Nuitka :)
#339 Standalone tests for botocore & boto3 + fix to Urllib3Using.py
- This PR was also created before the start of GSoC.
- Standalone test Boto3Using.py was created using moto to mock AWS calls which did not turn out well.
- Changed Urllib3Using.py with the addition of python version checks as a fix to Issue #373.
Urllib3 Wheel with Nuitka Pytest Results and Python-Dateutil Wheel with Nuitka Pytest Results
- At the start of GSoC, I performed manual pytest comparison for PyPI packages urllib3 and dateutil.
- The findings of my testing were documented in these postings.
- Manual testing compares the pytest results of an installed nuitka wheel built using python setup.py bdist_nuitka to the regular pytest results of each package.
- Testing is done to ensure that nuitka is building the wheel correctly.
- If the pytests pass/fail in the same way, that means Nuitka built the wheel properly.
- Else if the tests differ, then something is wrong.
- Virtualenv is used to create a clean environment with no outside pollution.
- Over the course of performing manual testing, I became familiar with the use of virtualenv, wheel, and pytest.
- A bug was found with the package urllib3 bdist and I created Issue #413 to document the bug.
#440 Automating PyPI Wheel Pytest
- After familiarizing myself with how virtualenv, wheel, and pytest work, I started to work on a script which would automate the pytest comparison for top PyPI packages.
- The script first uses git to update each package if it is already existing in the local cache, else it will git clone that package into the local cache.
- The script then uses calls to os.system to automate the creation of a virtualenv which is then used to install pytest and pip install the package’s requirements (if any) for running pytest.
- The script then handles each package depending on different needs before building a regular wheel with python setup.py bdist_wheel.
- This wheel is then installed into the virtualenv, after which subprocess.Popen is used to run and capture the output of python -m pytest --disable-warnings into a string.
- The script then resets the package to its original state and builds a nuitka-compiled wheel using python setup.py bdist_nuitka.
- This compiled wheel is then installed into the virtualenv, after which subprocess.Popen is used to run and capture the output of python -m pytest --disable-warnings into another string.
- The two strings containing pytest outputs are then compared to find differences.
- If no differences are found, this means bdist_nuitka worked properly. Else Nuitka compilation did something wrong.
- The above process is repeated for each suitable PyPI package from the PyPI top 50. (Some packages are left out if they do not contain a test suite or if they do not need to be tested)
- At the end, a colored summary is given for all the packages tested.
- This automation script is meant to be run regularly to inform developers of Nuitka regressions.
Issue #477 Unable to compile modules listed under unworthy_namespaces
- Raised due to package pycparser failing in the automated test suite.
- This issue will be addressed in the future.
Issue #479 bdist_nuitka fails for packages containing py_modules only
- While I worked on #440, I found a bug with bdist_nuitka failing on PyPI packages containing py_modules only.
- This bug occurs due to Nuitka making the assumption that a main package always exists for all packages. However, some packages contain only a main module and not a main package.
- Applies to PyPI packages decorator, ipaddress, and pyparsing.
#483 Add support for py_modules_only compilation
- This pull request changes bdist_nuitka.py and various other files to fix Issue #479.
- Checks are added for the bdist_nuitka command to see if a main package exists. If there is not a main package, it will set its compile target to the main module instead.
- This also addressed the case of a package with both a main package and a main module, in which case both are included inside the resulting wheel.
- In addition, distutils examples py_modules_only and package_and_module were created and added for future testing.
- During this PR, I found an import bug in Nuitka and hotfixed it with #487 Fixup_import_module.
#484 PyPI Standalone Tests
- This pull request adds more standalone tests for each top PyPI package.
#495 Improve pypi automation
- Improves the PyPI test suite created in #440 with functional improvements, readability improvements, and added documentation.

Things I Learned

Before GSoC, I was very uncomfortable with working inside a terminal. I was unfamiliar with many basic bash commands because I simply did not have any prior professional industrial experiences. I was also very unfamiliar with the Git flow, which is evident in the messy commit histories of my earliest pull requests.

As I continued throughout my GSoC journey, however, I became much more comfortable with working inside the terminal as well as using git as a version-control system (shoutout to my mentor Kay Hayen for helping me through all the annoying conflicts).

Although I am still no expert, I can confidently say that I am now far more proficient working with git and inside the terminal.

In addition, I became much more familiar with many of the most popular PyPI packages as well as the inner workings of python, which I believe will help me go very far in my career as a software developer.

Overall, the GSoC experience was truly astounding and I am more than thankful to my mentor Kay Hayen as well as Google for making this amazing program possible.

Yours, Tommy

Intro

2019-07-12T18:00:00+02:00

This post compares the pytest results of dateutil to its nuitka-built .whl counterpart.

Dateutil standalone test have already been covered. Manual testing is now done to compare the pytest results of a nuitka wheel built using python setup.py bdist_nuitka to the regular pytest of the dateutil package. Testing is done to ensure that nuitka is building the wheel correctly. If the pytests pass/fail in the same way, that means Nuitka built the wheel properly. Else if the tests differ, then something is wrong. Virtualenv is used to create a clean environment with no outside pollution.

The pytest results were very similar:

Regular pytests: ============= 1977 passed, 76 skipped, 21 xfailed in 7.99 seconds =============
Nuitka wheel pytests: ============= 1976 passed, 76 skipped, 21 xfailed in 7.89 seconds =============

Steps to Reproduce

Clone dateutil and nuitka into a new folder
Inside the dateutil folder, issue python -m pip install -r requirements-dev.txt to install its requirements.
Issue python -m pytest --disable-warnings, this runs the regular pytest for dateutil.
Change into the nuitka folder and issue python setup.py develop.
Change back into dateutil and issue python setup.py bdist_nuitka to build the dateutil wheel using nuitka. The newly built wheel should be found in the dist folder.
Use pip to uninstall the existing dateutil, then issue python -m pip install followed by the newly built .whl filename.
Issue python -m pytest --disable-warnings, this runs the nuitka-built wheel pytest for dateutil.

Uncompile Python

dateutil regular pytest:

============================= test session starts =============================
platform win32 -- Python 3.7.0, pytest-4.6.3, py-1.8.0, pluggy-0.12.0
rootdir: C:\Users\Tommy\pipenv-testing\dateutil-testing\dateutil, inifile: setup.cfg
plugins: hypothesis-4.24.3, cov-2.7.1
collected 2074 items

dateutil\test\test_easter.py ........................................... [  2%]
........................................................................ [  5%]
................................................                         [  7%]
dateutil\test\test_import_star.py .                                      [  7%]
dateutil\test\test_imports.py .......................                    [  9%]
dateutil\test\test_internals.py ....                                     [  9%]
dateutil\test\test_isoparser.py ........................................ [ 11%]
........................................................................ [ 14%]
........................................................................ [ 18%]
........................................................................ [ 21%]
........................................................................ [ 25%]
.......x...x............................................................ [ 28%]
........................................................................ [ 31%]
........................................................................ [ 35%]
.....................xx                                                  [ 36%]
dateutil\test\test_parser.py ........................................... [ 38%]
........................................................................ [ 42%]
........................................................................ [ 45%]
.................................xxxxxxxxxxxxxsss......                  [ 48%]
dateutil\test\test_relativedelta.py .................................... [ 49%]
.............................................                            [ 52%]
dateutil\test\test_rrule.py ............................................ [ 54%]
........................................................................ [ 57%]
........................................................................ [ 61%]
........................................................................ [ 64%]
........................................................................ [ 68%]
........................................................................ [ 71%]
........................................................................ [ 75%]
................................................................x....... [ 78%]
..............                                                           [ 79%]
dateutil\test\test_tz.py ............................s...........sssssss [ 81%]
sssssssssssssssssssssssssssssssssssssssss..s............................ [ 84%]
xxx..s......................................s........................... [ 88%]
s....................................................................... [ 91%]
..........s....................................s.s....................ss [ 95%]
sssssssssssss....s..........s........................................... [ 98%]
.............                                                            [ 99%]
dateutil\test\test_utils.py .......                                      [ 99%]
dateutil\test\property\test_isoparse_prop.py .                           [ 99%]
dateutil\test\property\test_parser_prop.py ..                            [ 99%]
docs\exercises\solutions\mlk_day_rrule_solution.py .                     [100%]

============= 1977 passed, 76 skipped, 21 xfailed in 7.99 seconds =============

Compiled with Nuitka

nuitka wheel pytest:

============================= test session starts =============================
platform win32 -- Python 3.7.0, pytest-4.6.3, py-1.8.0, pluggy-0.12.0
rootdir: C:\Users\Tommy\pipenv-testing\dateutil-testing\dateutil, inifile: setup.cfg
plugins: hypothesis-4.24.3, cov-2.7.1
collected 2073 items

test\test_easter.py .................................................... [  2%]
........................................................................ [  5%]
.......................................                                  [  7%]
test\test_import_star.py .                                               [  7%]
test\test_imports.py .......................                             [  9%]
test\test_internals.py ....                                              [  9%]
test\test_isoparser.py ................................................. [ 11%]
........................................................................ [ 15%]
........................................................................ [ 18%]
........................................................................ [ 21%]
......................................................................x. [ 25%]
..x..................................................................... [ 28%]
........................................................................ [ 32%]
........................................................................ [ 35%]
............xx                                                           [ 36%]
test\test_parser.py .................................................... [ 39%]
........................................................................ [ 42%]
........................................................................ [ 46%]
........................xxxxxxxxxxxxxsss......                           [ 48%]
test\test_relativedelta.py ............................................. [ 50%]
....................................                                     [ 52%]
test\test_rrule.py ..................................................... [ 54%]
........................................................................ [ 58%]
........................................................................ [ 61%]
........................................................................ [ 65%]
........................................................................ [ 68%]
........................................................................ [ 72%]
........................................................................ [ 75%]
.......................................................x................ [ 79%]
.....                                                                    [ 79%]
test\test_tz.py ............................s...........ssssssssssssssss [ 81%]
ssssssssssssssssssssssssssssssss..s............................xxx..s... [ 85%]
...................................s...........................s........ [ 88%]
........................................................................ [ 92%]
.s....................................s.s....................sssssssssss [ 95%]
ssss....s..........s.................................................... [ 99%]
....                                                                     [ 99%]
test\test_utils.py .......                                               [ 99%]
test\property\test_isoparse_prop.py .                                    [ 99%]
test\property\test_parser_prop.py ..                                     [100%]

============= 1976 passed, 76 skipped, 21 xfailed in 7.89 seconds =============

Intro

2019-06-19T16:00:00+02:00

This post compares the pytest results of urllib3 to its nuitka-built .whl counterpart.

Urllib3 standalone test have already been covered. Manual testing is now done to compare the pytest results of a nuitka wheel built using python setup.py bdist_nuitka to the regular pytest of the urllib3 package. Testing is done to ensure that nuitka is building the wheel correctly. If the pytests pass/fail in the same way, that means Nuitka built the wheel properly. Else if the tests differ, then something is wrong. Virtualenv is used to create a clean environment with no outside pollution.

At first, the urllib3 nuitka-wheel pytest was crashing because of the unsafe assumption that imports will always exist (which is not the case if exceptions are thrown). Issue 413 was filed to record and fix this bug.

After the fixes, the pytests were ran again and the results were very similar:

Regular pytests: ====== 3 failed, 836 passed, 456 skipped, 113 warnings in 47.54 seconds =======
Nuitka wheel pytests: ====== 1 failed, 838 passed, 456 skipped, 113 warnings in 47.59 seconds =======

The extra passes are suspicious and require more investigation into why they happen. To make that easy, we are going to fully automate the process and compare outputs with verbose pytest modes.

Steps to Reproduce

Clone urllib3 and nuitka into a new folder
Inside the urllib3 folder, issue python -m pip install -r dev-requirements.txt to install its requirements.
Issue python -m pytest --disable-warnings, this runs the regular pytest for urllib3.
Change into the nuitka folder and issue python setup.py develop.
Change back into urllib3 and issue python setup.py bdist_nuitka to build the urllib3 wheel using nuitka. The newly built wheel should be found in the dist folder.
Use pip to uninstall the existing urllib3, then issue python -m pip install followed by the newly built .whl filename.
Issue python -m pytest --disable-warnings, this runs the nuitka-built wheel pytest for urllib3.

Uncompile Python

urllib3 regular pytest:

$ python -m pytest --disable-warnings
============================= test session starts =============================
platform win32 -- Python 3.7.0, pytest-4.0.0, py-1.8.0, pluggy-0.11.0
rootdir: C:\Users\Tommy\pipenv-testing\urllib3-testing\urllib3, inifile: setup.cfg
plugins: timeout-1.3.1
collected 1295 items

test\test_collections.py ....................................s           [  2%]
test\test_compatibility.py ...                                           [  3%]
test\test_connection.py .....                                            [  3%]
test\test_connectionpool.py ............................................ [  6%]
...........................                                              [  8%]
test\test_exceptions.py .............                                    [  9%]
test\test_fields.py ...............                                      [ 11%]
test\test_filepost.py ...........                                        [ 11%]
test\test_no_ssl.py ..                                                   [ 12%]
test\test_poolmanager.py .........................                       [ 14%]
test\test_proxymanager.py ...                                            [ 14%]
test\test_queue_monkeypatch.py .                                         [ 14%]
test\test_response.py ..................sss............................. [ 18%]
...........                                                              [ 19%]
test\test_retry.py ..............................F.F.F..                 [ 21%]
test\test_ssl.py ...............................                         [ 24%]
test\test_util.py ...................................................... [ 28%]
........................................................................ [ 34%]
....................ss.s...s............................................ [ 39%]
............                                                             [ 40%]
test\test_wait.py ...ssssss                                              [ 41%]
test\contrib\test_pyopenssl.py sssssssssssssssssssssssssssssssssssssssss [ 44%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 49%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 55%]
ssssssssssssssssssss                                                     [ 57%]
test\contrib\test_pyopenssl_dependencies.py ss                           [ 57%]
test\contrib\test_securetransport.py sssssssssssssssssssssssssssssssssss [ 59%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 65%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 71%]
sssssssssssssssssss                                                      [ 72%]
test\contrib\test_socks.py ..................                            [ 73%]
test\with_dummyserver\test_chunked_transfer.py ........                  [ 74%]
test\with_dummyserver\test_connectionpool.py ........................... [ 76%]
.......................................                                  [ 79%]
test\with_dummyserver\test_https.py .....................s....s......... [ 82%]
.................................................Uncaught exception, closing connection.
........................................................................ [ 87%]
................................sssssssssssssssssssssssssssssssssss....  [ 93%]
test\with_dummyserver\test_no_ssl.py ..                                  [ 93%]
test\with_dummyserver\test_poolmanager.py ...............                [ 94%]
test\with_dummyserver\test_proxy_poolmanager.py ................         [ 95%]
test\with_dummyserver\test_socketlevel.py .............................. [ 98%]
......................                                                   [100%]
====== 3 failed, 836 passed, 456 skipped, 113 warnings in 47.54 seconds =======

Compiled with Nuitka

nuitka wheel pytest:

$ python -m pytest --disable-warnings
============================= test session starts =============================
platform win32 -- Python 3.7.0, pytest-4.0.0, py-1.8.0, pluggy-0.11.0
rootdir: C:\Users\Tommy\pipenv-testing\urllib3-testing\urllib3, inifile: setup.cfg
plugins: timeout-1.3.1
collected 1295 items

test\test_collections.py ....................................s           [  2%]
test\test_compatibility.py ...                                           [  3%]
test\test_connection.py .....                                            [  3%]
test\test_connectionpool.py ............................................ [  6%]
...........................                                              [  8%]
test\test_exceptions.py .............                                    [  9%]
test\test_fields.py ...............                                      [ 11%]
test\test_filepost.py ...........                                        [ 11%]
test\test_no_ssl.py .F                                                   [ 12%]
test\test_poolmanager.py .........................                       [ 14%]
test\test_proxymanager.py ...                                            [ 14%]
test\test_queue_monkeypatch.py .                                         [ 14%]
test\test_response.py ..................sss............................. [ 18%]
...........                                                              [ 19%]
test\test_retry.py .....................................                 [ 21%]
test\test_ssl.py ...............................                         [ 24%]
test\test_util.py ...................................................... [ 28%]
........................................................................ [ 34%]
....................ss.s...s............................................ [ 39%]
............                                                             [ 40%]
test\test_wait.py ...ssssss                                              [ 41%]
test\contrib\test_pyopenssl.py sssssssssssssssssssssssssssssssssssssssss [ 44%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 49%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 55%]
ssssssssssssssssssss                                                     [ 57%]
test\contrib\test_pyopenssl_dependencies.py ss                           [ 57%]
test\contrib\test_securetransport.py sssssssssssssssssssssssssssssssssss [ 59%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 65%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss [ 71%]
sssssssssssssssssss                                                      [ 72%]
test\contrib\test_socks.py ..................                            [ 73%]
test\with_dummyserver\test_chunked_transfer.py ........                  [ 74%]
test\with_dummyserver\test_connectionpool.py ........................... [ 76%]
.......................................                                  [ 79%]
test\with_dummyserver\test_https.py .....................s....s......... [ 82%]
........................................................................ [ 87%]
................................sssssssssssssssssssssssssssssssssss....  [ 93%]
test\with_dummyserver\test_no_ssl.py ..                                  [ 93%]
test\with_dummyserver\test_poolmanager.py ...............                [ 94%]
test\with_dummyserver\test_proxy_poolmanager.py ................         [ 95%]
test\with_dummyserver\test_socketlevel.py .............................. [ 98%]
......................                                                   [100%]
====== 1 failed, 838 passed, 456 skipped, 113 warnings in 47.59 seconds =======

Jorj X. McKie

2019-05-18T11:00:00+02:00

Self-Introduction Jorj McKie

Hello everyone,

I am Jorj X. McKie (this is not my real name!) and I am an enthusiastic supporter of Nuitka. For the time being, my focus area within this package is standalone compilation and maintenance of the plugin feature.

Apart from extending Nuitka’s support to virtually all Python packages living out there, my driving motivation in this respect is keeping up and improving the usability of Nuitka.

You may want to look into the Nuitka Utilities repository, which contains many things I am working on.

alert alert-primary float-md-right

Short Biography

Born 1951 as Harald Lieder near the city of Leipzig
Studied Mathematics and Physics at the Frankfurt/M Johann-Wolfgang-Goethe University from 10/1970 through 06/1976 (Diploma in Mathematics)
Professional career overview
- insurance company (4 years): application and systems programming (IBM mainframe, Cobol, Assembler), data center lead
- book wholesaler (5 years): systems programming and data center lead (IBM mainframe)
- consulting company (until 2009): leading of or participating in numerous large and very large projects mostly around banking applications, banking mergers, data center optimization and quality assurance.
- since 2009: retirement, living on Isla Margarita, Venezuela. Enjoying my beautiful house, pursuing my hobbies: mathematics, science theory, biological evolution theory, science fiction (my pseudonym comes from novels by one of my favorite authors Frank Herbert) and of course programming (maintainer of PyMuPDF, and Nuitka).

Images from Isla Margarita

House Frontview with Guardians

In favorite Pizzeria with my Wife

Seaview from my Terrace

Sunrise view from House

Tommy’s Google Summer of Code Intro

2019-05-15T10:00:00+02:00

Hi all! :)

My name is Taofeng Li and I go by the nickname of Tommy, github handle tommyli3318. I’m a Computer Science major at the University of California, Irvine in the United States. I am very excited to announce that I’ll be contributing to Nuitka this summer under the Google Summer of Code program!

My project is “Nuitka support for PyPI top 50”, it ensures Nuitka’s compatibility with the 50 most popular PyPI packages by setting up automated testing for each package. These automated tests will serve to be very important tools for the development of Nuitka, as they will be used to assure Nuitka’s compatibility with the most used Python packages every time Nuitka receives a new update.

My mentors will be Vaibhav Tulsyan, Kamran Ghanaat, and Kay Hayen. My project abstract can be seen here and the full details of my project can be found here.

I am greatly looking forward to the many things that I’ll learn this summer!

Batakrishna Sahu

2019-05-14T08:31:00+02:00

Hello everyone!

My name is Batakrishna Sahu and I am from India. I’m very grateful to be one of the 2 selected students who will work with Nuitka during Google Summer of Code 2019. My project is on “Optimizing Python 2 and Python 3 built-ins for Nuitka” mentored by Vaibhav Tulsyan, Kamran Ghanaat, Kay Hayen.

So far, there are a total of 69 built-ins in Python 3 and 76 built-in in Python 2 out of which 27 built-ins are yet to be optimized in Nuitka. My aim is to optimize those missing built-ins in Nuitka. This will make Nuitka a lot faster while working with built-ins.

I’m really excited to gain new experience while working on this project this summer.

Yours,

Batakrishna