quantum-algorithms

Is your feature request related to a use case or problem? Please describe.
Right now a lot of modules (in particular tests) are pretty free form with how they do imports. It's a good practice to import modules wherever possible.

bad:

from cirq.devices import GridQubit

good:

from cirq import devices

devices.GridQubit(whatever)

**Describe the soluti

To get this codebase up to standard, we need to add type hints. At the very least, perhaps we should start insisting that all new code has type hints added, but moreover we need to add typing to the code that currently exists.

This is a pretty large project, but luckily it can be done incrementally - I believe at this point it's a stretch goal for v1, if anyone wants to help it would be much ap

начало обсуждения тут

Whenever a slide has minted code, like so:

\begin{frame}[fragile]{Example minted}
	\begin{minted}{python}
		from qiskit_aqua import run_algorithm

		print(run_algorithm(params)['result'])
	\end{minted}
\end{frame}

One is unable to add the \pagenumber before \end{frame} as it gets left aligned instead of right aligned:
![image](https://user-images.githubusercontent.com/1

RDMs returned from pyscf are spin summed. Use https://sunqm.github.io/pyscf/_modules/pyscf/fci/direct_spin1.html#FCISolver.make_rdm12s

to return non-spin summed versions. Recombine spin-separated RDMs like run_psi4 to get spin-orbital rdms before returning to OpenFermion.

Now that Q# + Python can use project files for references, we should add them here so IntelliSense can work better :)