from Construct developer, a note

[arekbulski]

I am the developer of Construct (a parsing library) since I took over the project 2 years ago. Please refer any other projects that also use this library to this post, or copy it over to them.

Construct is undergoing heavy changes at the moment, similar to those between 2.5->2.8, including addition of compiler feature (to make it much faster than Kaitai), but also several classes are going to be removed (for a good reason), and also few were added. API will be unstable for about a month.

What you can do:

• All scheduled work is posted as tickets, in Issues and also on Kanban page. If you subscribe (watch repository) then you will have advance notice of any incoming changes. Unfortunately those tickets also include minor work items, so you would get some clutter notifications too. I appologise for that.
• I encourage everyone to browse those tickets, vote for feature requests, but also post objections for planned removal of features, or changes in semantics. Subscribing therefore is recommended.
• You can find what was already changed (at any moment) on Transition page, which is like a growing changelog. It gets updated whenever something gets added or removed, but since the order is not chronological, new items do not end up on top or bottom of the list.
• You can find currently available classes and semantics on revamped Core API pages. Those pages are very extensive and always uptodate with the implementation.
• Feel free, at any point in time, to open a new Issue and ask questions or make complaints about breakage. At minimum, I can offer advice and possible alternatives. People very often use the classes in ways that were not designed for, like use String classes to process Bytes.
• Feel free, at any point in time, to open a new Issue and request changes. If you need a new class, and make a good clear case, I would be more than willing to add it to core library to support your project.
• API should be stable within a month, so either do version pinning and deal with it then, or keep fixing your code at every release (which is ~3 day cycle at the moment).

Close this topic at your discretion.

[arekbulski]

Could you grant me write access so I could work on patches on local branches?

[rytilahti]

PRs fixing issues & improving things are very welcome. We use that as a mechanism to allow easier code reviews & pre-commit QA to keep everyone involved in a loop.

[arekbulski]

I am going to use PRs but its a pain in the butt to pull from forked repository. Much easier to work on local side-branch when doing PRs.

[yawor]

I've added this repo as "upstream" remote and then configured my local master branch to use it by default (git config branch.master.remote upstream).

[arekbulski]

How can I make this repo "upstream", thats a different command, right?

[yawor]

If you have a local clone of your python-miio fork on github, then:

git remote add upstream https://github.com/rytilahti/python-miio.git
git config branch.master.remote upstream

then

git checkout master
git pull

should pull master branch from this repository to your local master branch by default.
You can always force specific remote:

git pull origin master
git pull upstream master

Of course the name "upstream" can be anything you want. It's just a name. I like "upstream" as it clearly describe what it is.

[arekbulski]

How does git pull --all fit in this picture?

[yawor]

My local repo is up to date, so it's hard to tell but:

% git pull --all
Fetching origin
Fetching upstream
Already up to date.

[arekbulski]

Thats very helpful, thanks. I used to just delete the fork repo and re-fork it. 😕

[yawor]

You need to remember though that this will not automatically keep your github fork's master branch up to date. It just point your local branch to pull from this repo by default. If, for some reason, you want to also keep your origin/master up to date, then after pulling from here, you need to run:

git checkout master
git push origin master

But I think this is not really necessary.

[arekbulski]

Thanks again for the tutorial @yawor . I learned something useful.