On 07/06/18 03:23, Jeff King wrote:
> On Thu, Jun 07, 2018 at 01:16:14AM +0100, Ramsay Jones wrote:
>
>>> Probably. We may want to go the same route as we did for perl in
>>> a0e0ec9f7d (t: provide a perl() function which uses $PERL_PATH,
>>> 2013-10-28) so that test writers don't have to
On Wed, Jun 06, 2018 at 10:23:53PM -0400, Jeff King wrote:
> Though maybe I am wrong that the remote-svn stuff requires python. I
> thought it did, but poking around, it looks like it's all C, and just
> the "svnrdump_sim" helper is python.
I think I was getting this mixed up with the
On Wed, Jun 06, 2018 at 09:49:09PM -0400, Todd Zullinger wrote:
> Ramsay Jones wrote:
> [...]
> > I don't run the p4 or svn tests, so ... :-D
>
> Heh, lucky you. :)
>
> I try to run them all as part of the fedora builds since
> they cover much more than I'd ever use. That's the main
> reason I
On Thu, Jun 07, 2018 at 01:16:14AM +0100, Ramsay Jones wrote:
> > Probably. We may want to go the same route as we did for perl in
> > a0e0ec9f7d (t: provide a perl() function which uses $PERL_PATH,
> > 2013-10-28) so that test writers don't have to remember this.
> >
> > That said, I wonder if
Ramsay Jones wrote:
[...]
> I don't run the p4 or svn tests, so ... :-D
Heh, lucky you. :)
I try to run them all as part of the fedora builds since
they cover much more than I'd ever use. That's the main
reason I noticed the bare python. That would trip me up
when it came time to build on a
On 06/06/18 22:03, Jeff King wrote:
> On Wed, Jun 06, 2018 at 01:10:52PM -0400, Todd Zullinger wrote:
>
>> g...@jeffhostetler.com wrote:
>>> +# As a sanity check, ask Python to parse our generated JSON. Let Python
>>> +# recursively dump the resulting dictionary in sorted order. Confirm that
On 6/6/2018 5:03 PM, Jeff King wrote:
On Wed, Jun 06, 2018 at 01:10:52PM -0400, Todd Zullinger wrote:
g...@jeffhostetler.com wrote:
+# As a sanity check, ask Python to parse our generated JSON. Let Python
+# recursively dump the resulting dictionary in sorted order. Confirm that
+# that
On 6/6/2018 1:10 PM, Todd Zullinger wrote:
g...@jeffhostetler.com wrote:
+# As a sanity check, ask Python to parse our generated JSON. Let Python
+# recursively dump the resulting dictionary in sorted order. Confirm that
+# that matches our expectations.
+test_expect_success PYTHON 'parse
On Wed, Jun 06, 2018 at 01:10:52PM -0400, Todd Zullinger wrote:
> g...@jeffhostetler.com wrote:
> > +# As a sanity check, ask Python to parse our generated JSON. Let Python
> > +# recursively dump the resulting dictionary in sorted order. Confirm that
> > +# that matches our expectations.
> >
g...@jeffhostetler.com wrote:
> +# As a sanity check, ask Python to parse our generated JSON. Let Python
> +# recursively dump the resulting dictionary in sorted order. Confirm that
> +# that matches our expectations.
> +test_expect_success PYTHON 'parse JSON using Python' '
[...]
> + python
From: Jeff Hostetler
Test json-writer output using Python.
Signed-off-by: Jeff Hostetler
---
t/t0019-json-writer.sh | 38 ++
t/t0019/parse_json_1.py | 35 +++
2 files changed, 73 insertions(+)
create mode 100644
11 matches
Mail list logo
