Currently, most samples only have a C# host program. It would be nice if more or even most samples demonstrated how to use Python to call into Q#.

Samples with Python Hosts

• algorithms
  • chsh-game
  • database-search
  • integer-factorization
  • oracle-synthesis
  • order-finding
  • reversible-logic-synthesis
  • simple-grover

• arithmetic

From Qiskit/qiskit-terra#3196 (comment), @nonhermitian says:

Match the upcoming changes to IQX circuit composer styling.

The closed PR #3196 suggests a new set of colors the the MPL circuit drawer. However, the PR got out-of-sync.

Please, use PR #3196 as a reference to set the new colors and run binder (see Qiskit/qiskit-terra#4544 as

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.

Running travis lint gives a bunch of warning. Like for instance, sudo : required is no longer needed, and Travis migrated to a new architecture. So the travis.yml file needs to be updated.

https://blog.travis-ci.com/2018-10-04-combining-linux-infrastructures

Is your feature request related to a problem? Please describe.
Deprecation warnings are raised for code used in deprecated functions or operations, even when they are never used.

Describe the solution you'd like
I would like no warning to be raised in this case.

Now, there's no unit test.

The description here of "declares if a classical condition is true" isn't very clear. From what I understand, if the classical condition is true, nothing happens and computation is continued, whereas if false, it aborts computation and no further Q# code is run. The failure/abort point coul

It would be helpful to add a tutorial explaining how to run things in parallel (mpirun etc). There are some users who are not familiar with mpi (see #173 ) and it is useful to explain the basic steps to do this.

We need to create a Q.History documentation page that is similar in nature to the existing Q class documentation pages. See Q-ComplexNumber.html as an example.

Please describe what you would like the feature to accomplish.
It can be really helpful to write unit tests that should fail (e.g.: checking that a new assertion or fact correctly identifies when a condition is not met). In the legacy testing framework, this could be accomplished with a C# test operation finder of the following form:

        [OperationDriver(Suffix = "TestShouldFail

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