| Age | Commit message (Collapse) | Author |
|---|
|
There is no pythonic way of specifying the version of a project, [0]
describes 7 (seven!) ways of doing it. We were currently using method
5, setting the value in setup.py and using pkg_resources to get it from
the installed version. This works ok if you have installed the package
using python setup.py or pip, but fails if you are importing bart from a
checkout, which is what lisa do. Even worse, if you import it from lisa
but have an old bart version installed, bart.__version__ will tell you
the version of the installed bart, not the one you have imported and are
using.
Switch to use a version.py file that's distributed with the
project (method 3), as trappy did in ARM-software/trappy@712e6f93b308 .
Fixes #57
[0] https://packaging.python.org/en/latest/single_source_version/
|
|
|
|
|
|
|
|
|
|
|
|
trappy has changed the API of stats.SchedConf in 0fce01a7dad8 ("stats:
SchedConf: Fix for period calculation"), the return value of period() is
changed. This is fixed in bart in 0e83faeeee8a ("sched: Use Median for
calculation of the period of a task").
|
|
|
|
trappy has changed the API for EventPlot in f4eefc02239a ("plotter:
EventPlot: Allow specification of lane names") which will be released
in trappy 2.0. This is fixed in 5b1275f59fec ("sched: Update usage of
EventPlot API") in bart. Make sure bart the next version of bart
depends on the appropriate version of trappy.
|
|
This will break as soon as we update trappy. Let's not require a
specific version until we know there are incompatibilities.
|
|
Bart is already taken by some software to model the light curves of
exoplanet transits.
|
|
|
|
Signed-off-by: Kapileshwar Singh <kapileshwar.singh@arm.com>
|
