Configuration #1665

Feature #418: === Configuration & Build ===

Take swig-generated Python wrappers out of git repository

Added by wuttke almost 3 years ago. Updated almost 3 years ago.

Status:RejectedStart date:23 Nov 2016
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Little API changes cause huge changes of the swig-generated wrappers.
This bloats the git file system, and in particular it bloats the log, which makes it more cumbersome to search them.

We had discussed this earlier, but I think our decision was wrong.
It is no significant burden for a developer to run cmake with option -DBORNAGAIN_GENERATE_BINDINGS=ON after a pull.

History

#1 Updated by herck almost 3 years ago

Another solution could be to severely limit the public API we export to Python. This would result in regeneration of the binding files only when this subset (=public API) changes. As a free bonus, this enables us to quickly track API changes.

#2 Updated by wuttke almost 3 years ago

  • Status changed from Rfc to Rejected

Agreed. Restriction of the Python API now requested by #1685.

Also available in: Atom PDF