Update shebangs to python3.

format-json

-#!/usr/bin/env python
+#!/usr/bin/env python3
 r"""Command-line tool to format software release JSON for slapos.
 
 Inspired by json.tool from python, but enforcing 2 spaces and non-sorted keys.

update-hash

-#!/usr/bin/env python
+#!/usr/bin/env python3
 """
 Helper script to update buildout.hash.cfg
 

validate-schema

-#!/usr/bin/env python
+#!/usr/bin/env python3
 import argparse
 import json
 import os.path

[Jérome Perrin]

this script is not python3 compatible, it imports from urllparse, we can maybe run 2to3 on it, I tried locally but I don't know how this script work and I think the functionality is built in slapos request now - it prints a warning if the parameters do not match schema, maybe nowadays we can just remove this script ?

[Ophélie Gagnard]

I'm OK with deleting the script. @tomo

[Thomas Gambier]

Yes, we can delete it. Or @rafael updates it to validate the schema using the meta schema existing now.

@rafael do you confirm you write the meta schema describing the schema supported by rapidspace master ?

[Rafael Monnerat]

I dont know this script, but I had been working on create more precise schemas some time ago:

• https://lab.nexedi.com/nexedi/slapos.core/blob/master/master/bt5/slapos_jio/PathTemplateItem/web_page_module/rjs_slapos_load_meta_schema_xml_in_json_json.txt
• https://lab.nexedi.com/nexedi/slapos.core/blob/master/master/bt5/slapos_jio/PathTemplateItem/web_page_module/rjs_slapos_load_meta_schema_xml_json.txt

The reason to create precise schemas were that we don't support ANY schema. For example, xml serialisation is a flat list of single value strings, so you cannot use sub objects (nothing to do with the form parameter), and numeric values will be seen as string later when it is sent to the instance.