Nuitka Blog - Posts tagged git

Nuitka on GitHub, Bitbucket and Gitorious

2013-04-26T07:17:16+02:00

This is to let you know, that I have finally carved in and created accounts on all those “social” platforms, that deal with code. So far I had resisted their terms (you pay us when we get sued), but I have given up on that stance, it’s likely irrelevant, as Nuitka won’t get sued, and if it is, those are not the issues.

And I don’t want to feel too old school it seems. And who knows, maybe this helps Nuitka to get more contributions.

So these are the landing pages:

Bitbucket (since deleted)

I kind of like the looks of it the most. Also it’s very popular for Python people due to its Mercurial ties. I also liked that it imported my Nuitka repository easily.
GitHub

Is not being on GitHub allowed these days? Anyway, from ease of use, the interface looks more powerful.
Gitorious (since discontinued)

The interface and looks definitely are worst. But it’s Free Software, and an open platform, so it has to be in the list.

Let me know what you think. I am going to push ‘develop’ at pre-release and ‘master’ at release time, automatically from the release scripts into all these. Hopefully that way, they turn out to be time savers no wasters.

And yes, I couldn’t decide on one. Since I fancy Free Software, Gitorious probably would have won, but it would also miss the point of expanding the reach. And for as long as I don’t use their issue tracking or Wikis, it appears to be not necessary to make that decision.

Note

The preferred for use, and most up to date repository will remain the one from Downloads.

So fork away, like it, and stuff. Awaiting your pull requests…

Nuitka - PyCON DE Video

2011-10-22T06:39:00+02:00

Hello everybody,

the Video of my presentation is online: https://pyvideo.org/pycon-de-2011/nuitka-der-python-compiler.html

Leaving it to Mike Müller to announce here the links to everything, when it’s all finished. Thanks for the good work, the video was very well done.

Update

The video is also available via Youtube.

Yours,

Kay

Nuitka git-flow

2011-10-01T08:37:00+02:00

Hello there,

this is to let you know that I have switched Nuitka to the “git flow” development model. That means, now there is a supported stable version, and a develop branch, together with feature branches.

Example

Git flow example for Nuitka release 0.3.12

Note

In case, you want and can improve the source (link since removed) visually or otherwise, please go ahead. I am using it for a presentation next week too, and would be glad if you could make it more pretty. My artistic skills are not the same as my programmer skills. :-)

So there is now always at least these 2 branches:

Stable (master branch)
Unstable (develop branch)

and then there may be feature branches, like this one currently:

Feature branch minimize_CPython26_tests_diff

These will only have certain life, until they are completed, then they are merge into “develop” and become part of the next release. This may or may not happen, depending on how things go.

Benefits of the new model

Hotfixes, typically bug fixes, can be made simultaneously on stable and develop branch. The git-flow package takes care of the merging to both.
Because that’s so easy now, a stable version can be provided and supported for a longer time.
Features can be published while under development. My idea is that feature branches should basically work, but the bar will be lower. People can have a look at them, or start their own and make me integrate them.

Uses of Feature Branch

For example, in the new feature branch, a couple of boring things are happening. Support for frame stack will reduce the diff, as will some work to match CPython’s choices for exception line numbers. Completing will take a while, but should not block a release. So this is best done in the feature branch, esp. as nothing is going to really depend on it.

General Picture

As you can see from this diagram, I am working mostly on documentation things. The new and improved README on develop, which is closer to a User Manual in PDF form, and other organization things, may get a release before the PyCon DE next week. The README also describes this process.

Hope is that with this approach, I will improve transparency (you can see earlier what i am working on, because there is now a place where things may break (develop) or may not yet be integrated or completed fully (feature branches) and yet be public.

The overhead appears to minimal thanks to “git-flow”. Developing hotfixes is actually easier, when done on the stable branch, because problems cannot originate from the current development work that may or may not be all that perfect yet.

Yours,

Kay Hayen

Nuitka has a new home - nuitka.net

2011-08-16T18:21:00+02:00

Hello everybody,

my new vServer is now online, the old site blog redirects to it now, and planets follow the new site already. The old site is redirecting with 301 error code for some more time, hopefully this will be good enough of a migration. It felt smooth from here, clearly, and the new site is much faster of course, because it’s not throttled through my poor DSL upstream.

I also registered it a domain name “nuitka.net” for it finally. Originally I wanted to give it a DynDNS name, but I already have 2, and the third was supposed to cost money, and I didn’t feel like using another service, or cheating them if you consider that an option, so that was it, I bought the domain name. Clearly it will also be easier for people to remember.

Moving things over was pretty painless. The Wordpress software has a pretty good export feature, which only didn’t manage the custom menu and appearance settings. But I guess it’s about content anyway, so probably some way that would work too, but it was easy enough to reproduce that by hand. I appreciate Wordpress even more now.

Also I did some tuning of the system, to use less memory. Only 512M are available, and so I run less Apache processes for less requests (memory leaks), disabled IPv6 (yes, hate me for it), reduced amounts of gettys, and so on. Nothing I am not familiar with, the ARM machine had 512M as well, and to me no reason to use the bigger package just because of that.

The main difference is the faster CPU, I seem to get 3Ghz Intel now, instead of my 1Ghz ARM, which together with faster internet speed, makes the site extremely fast.

Now U will dare to make the gitweb interface public as well. The git repository is already running there.

Note

This is obsolete information, we use GitHub for this now.

And I took the chance to sanitize the old posts somewhat. Changed the links to not use the old domain name anymore, and correct some broken ones too.

Only downside is that I currently haven’t got the “speedcenter” up and running again. After losing my hardware, the old data cannot be compared with new one, and then it doesn’t feel like a priority right now. I seem to be working instead on XML based regression tests of the optimizer: The output of “–dump-xml” should be compared for a large quantity of files, to discover regressions of the optimizer as soon as possible, this will enable me to make changes and not have to review the C++ as much, to find out if something is compiled correctly. This way I should detect it when known good cases degrade, and generally to demonstrate better, what actually did improve.

Yours,

Kay Hayen

PS: Oh, you people, who wonder, “but why are you not using Google/github/gitorious?”, my counter question: “Did you read the agreement?” I did. It basically says (from Google code):

13. INDEMNITY

You agree to hold harmless and indemnify Google, and its subsidiaries, affiliates, officers, agents, employees, advertisers, licensors, suppliers or partners, (collectively "Google and Partners") from and against any third-party claim arising from or in any way related to your use of Google services, violation of the Terms or any other actions connected with use of Google services, including any liability or expense arising from all claims, losses, damages (actual and consequential), suits, judgments, litigation costs and attorneys' fees, of every kind and nature. In such a case, Google will provide you with written notice of such claim, suit or action.

No thank you, instead I will run my own server, then I get to pay the attorneys of my discretion - in the admittedly unlikely event that somebody should sue me, because my Compiler violates some patent, or whatever.

Yours,

Kay

Nuitka Pre-Release 0.3.4pre1

2010-12-06T23:27:00+01:00

This pre-release of Nuitka has a focus on re-organizing the Nuitka generated source code. Please see the page “What is Nuitka?” for clarification of what it is now and what it wants to be.

For a long time, Nuitka has generated a single C++ file, even when embedding many modules into one. And it has always showed that the GNU g++ compiler clearly has exponential compile time behavior when translating these into the executable.

This is no more the case. So this pre-release is mainly about making the --deep feature useful. Before the release, I may look into optimizations for speed again. Right now time is very short due to day job reasons, so this pre-release is also about allowing people to use the improvements that I have made and get some feedback about it.

Bug fixes

None at all. Although I am sure that there may be regressions on the options side. The tests of CPython 2.7 all pass still, but you may find some breakage.

Cleanups

Static helpers source code has been moved to “.hpp” and “.cpp” files, instead of being in “.py” files.
Generated generated code for each module is now a separate file.
Constants etc. go to their own file (although not named sensible yet)

New Features

Uses Scons to make the build.

New Tests

I have added ExtremClosure from the Python quiz. I feel it was not covered by existing tests yet.

Organizational

There is now a new environment variable “NUITKA_SCONS” which should point to the directory with the Scons file for Nuitka.
The create-environment.sh can now be sourced (if you are in the top level directory of Nuitka) or be used with eval. In either case it also reports what it does.

Numbers

None at this time. It likely didn’t change much at all. And I am not yet using the link time optimization feature of the g++ compiler, so potentially it should be worse than before at max.

This release will be inside the “git” repository only. Check out latest version here to get it.

Yours,

Kay Hayen

New git repository to sync with Nuitka releases

2010-08-26T23:06:00+02:00

For you git fans out there I have just added a new method to download Nuitka from something I call the release git repository:

git clone http://git.nuitka.net/Nuitka.git

Then do your own modifications, and do:

git pull --rebase

each time there is a new release. You will be led through the merge process as usual. To reduce your differences, feel free to send me the patches you create with:

git format-patch <commit-id>

and I will incorporate useful stuff.

Please note

If you publish your own git repository, please be so kind and name it “Nuitka-unofficial” or similar, or else it might be mistaken with the real thing, and drop me a line about it, just so I know.

Kay Hayen