musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks.

musicxml2ly: handle hidden time signatures; support text+bpm \tempo marks.

[a.myltsev, 2018-06-01 11:19:31]

musicxml2ly: hidden time signatures and tempo marks with text.

[a.myltsev, 2018-06-01 11:49:06]

musicxml2ly: hidden timesigs and tempo marks with text.

[a.myltsev, 2018-06-01 11:49:56]

musicxml2ly: hidden timesigs and tempo marks with text.

[a.myltsev, 2018-06-01 11:50:31]

musicxml2ly: hidden timesigs and tempo marks with text.

[lilypond-pkx, 2018-06-01 16:06:59]

On 2018/06/01 11:50:31, a.myltsev wrote:
> musicxml2ly: hidden timesigs and tempo marks with text.

What are the scripts these 'test' dirs?

Was this a mistake?

If so can you re-submit the patch please?

thanks

James

[a.myltsev, 2018-06-01 20:12:25]

> What are the scripts these 'test' dirs?

Those are actual tests for the added functionality, runnable with `pytest`.

> Was this a mistake?

No, I believe that these tests are individually useful, even though not yet
integrated into the Lilypond testing system. If you prefer, though, I can leave
them out.

[lilypond-pkx, 2018-06-02 17:46:02]

On 2018/06/01 20:12:25, a.myltsev wrote:
> > What are the scripts these 'test' dirs?
> 
> Those are actual tests for the added functionality, runnable with `pytest`.
> 
> > Was this a mistake?
> 
> No, I believe that these tests are individually useful, even though not yet
> integrated into the Lilypond testing system. If you prefer, though, I can
leave
> them out.

Yes if you wouldn't mind, that would be better I think. 

We should only be testing 'a patch' that has components that are 'push ready'
(so  to speak).

If you want to add some more 'tests' then I suggest the best way would be to
create a new tracker for them that you can start a discussion separate from the
other work you have done.

However, if these tests are integral to this work and you intend to eventually
integrate them with the other work in this patch then that is fine too, but it
wasn't clear to me.

I'll wait to see what you want to do.

Thanks for your understanding.

[a.myltsev, 2018-06-04 10:51:25]

Removed the 'test' commits, leaving only changes to Python files.

[lilypond-pkx, 2018-06-13 14:38:23]

On 2018/06/04 10:51:25, a.myltsev wrote:
> Removed the 'test' commits, leaving only changes to Python files.

Patch counted down - please push. Alex if you do not have commit access can you
attach a git-formatted patch (re-based against current master) and I can push it
for you - attach it to the tracker, I will see it -
https://sourceforge.net/p/testlilyissues/issues/5333/

[lilypond-pkx, 2018-06-16 10:04:24]

On 2018/06/13 14:38:23, lilypond-pkx wrote:
> On 2018/06/04 10:51:25, a.myltsev wrote:
> > Removed the 'test' commits, leaving only changes to Python files.
> 
> Patch counted down - please push. Alex if you do not have commit access can
you
> attach a git-formatted patch (re-based against current master) and I can push
it
> for you - attach it to the tracker, I will see it -
> https://sourceforge.net/p/testlilyissues/issues/5333/

author  Alexander Myltsev <a.myltsev@gmail.com> 
    Wed, 27 Apr 2016 16:04:43 +0100 (18:04 +0300)
committer   James Lowe <pkx166h@runbox.com> 
    Sat, 16 Jun 2018 10:58:59 +0100 (10:58 +0100)
commit  d751f5fd70d1c4de9878dceb81bda42e9a500fb7

author  Alexander Myltsev <a.myltsev@gmail.com> 
    Thu, 2 Jun 2016 09:19:07 +0100 (11:19 +0300)
committer   James Lowe <pkx166h@runbox.com> 
    Sat, 16 Jun 2018 10:59:08 +0100 (10:59 +0100)
commit  7b07440da921d979ab492fd284b6198152a8020c

Many thanks Alexander.