Open dbcq opened 1 year ago
Could you advise what to do about the failed linting? I assume it comes from the long 'comments' which are turned into markdown cells by p2j
. pytket-quantinuum seems to have the same formatting but appears to lint fine, but I couldn't see any particular options which were being used there
Could you advise what to do about the failed linting? I assume it comes from the long 'comments' which are turned into markdown cells by
p2j
. pytket-quantinuum seems to have the same formatting but appears to lint fine, but I couldn't see any particular options which were being used there
Yes it seems to be coming from the long lines. Can you wrap the lines at 80 characters. or does that break the p2j conversion? If necessary we can exclude the folder from the link check.
Yes, p2j
treats each line break as a new markdown cell so it doesn't look the best. I assume in pytket-quantinuum
they're simply excluded from the linting check
Yes,
p2j
treats each line break as a new markdown cell so it doesn't look the best. I assume inpytket-quantinuum
they're simply excluded from the linting check
Actually they are not excluded there, and the python files do contain long lines (e.g. https://github.com/CQCL/pytket-quantinuum/blob/develop/examples/python/Quantinuum_circuit_submissions.py ), so I am not sure what's different here...
I think it'd be nice to have an example as some of the syntax for pytket-braket can be confusing. Should we finish this off?
I think it'd be nice to have an example as some of the syntax for pytket-braket can be confusing. Should we finish this off?
Sure, I think it's just some linting issues to fix?
Please rebase and retarget to main
which is now the default branch.
Amazon braket documentation is sometimes not very clear, and
pytket-braket
doesn't have as much documentation as some otherpytket
extensions. This notebook is based on a Confluence page I wrote for our team and on a notebook by Callum. I have used the notebook template and generation frompytket-quantinuum
.