Develop Reference

Python - Difference between Sonarcube Vs pylint

I'm evaluating test framework, lint and code coverage options for a new Python project I'll be working on.
I've chosen pytest for the testing needs. After reading a bunch of resources, I'm confused when to use Sonarcube, Sonarlint , pylint and coverage.py.
Is SonarLint and Pylint comparable? When would I use Sonarcube?
I need to be able to use this in a Jenkins build. Thanks for helping!

Sonarlint and pylint are comparable, in a way.
Sonarlint is a code linter and pylint is too. I haven't used sonarlint, but it seems that analyzes the code a bit deeper that pylint does. From my experience, pylint only follows a set of rules (that you can modify, by the way), while sonarlint goes a bit further analyzing the inner workings of your code. They are both static analyze tools, however.
Sonarcube, on the other hand, does a bit more. Sonarcube is a CI/CD tool that runs static linters, but also shows you code smells, and does a security analysis. All of what I'm saying is based purely on their website.
If you would like to run CI/CD workflows or scripts, you would use Sonarcube, but for local coding, sonarlint is enough. Pylint is the traditional way, though.

Nicholas has a great summary of Pylint vs Sonarlint.
(Personally I use the Sonarlint)
Although the question is older, I thought I'd answer the other part of your question in case anyone else has the same question; internet being eternal and all.
Coverage.py as it sounds, runs code coverage for your package. SonarQube then uses the report that coverage.py makes and does things with it and formats it in a way that the Sonar team decided was necessary. Coverage.py is needed if you want to use SonarQube for code coverage. However, if you just want the code smells from SonarQube, it is not needed.
You were also asking about when to use SonarQube, coverage.py, and Jenkins.
In Jenkins, you would create a pipeline with several stages. Something along the following lines:
Check out code (automatically done as the first step by Jenkins
Build code as it is intended to be used by user/developer
Run Unit Tests
run coverage.py
run SonarQube

How to run adev(aiohttp_devtools) command using PyCharm

I want to use PyCharm debugger with aiohttp_devtools, but have no idea how to run command:
adev runserver --no-livereload
in this window

Add a new file to run the CLI and reference that in the debug setup:
adev.py:
from aiohttp_devtools.cli import cli
if __name__ == '__main__':
cli()
Then reference that to setup debugging:
With that everything worked fine for me.
Context:
I've fixed the issue above referenced by Andrew #99 and will create a new release v0.5.0, however that doesn't actually fix the problem here. I'll explain how to get debug working below.
I do use pycharm, but I steer clear of debug and similar features: partly because (as in this case) they're generally not worth the effort, and partly so when someone comes up with a decent opensource or paid IDE for python I can get away from pycharm's awful bugginess and awful customer service without much hassle.
The thing to remember when wrestling with pycharm is it was built by java developers in a hurry, not python developers; so it often deviates significantly from the pythonic way of doing things.
For example, in this case the developer clearly hadn't heard about python -m "run module as a script" or the virtualenv env/bin extension to $PATH.

Thank you for raising the question.
Right now there is no easy way to do it.
The only solution is creating own custom startup script which instantiates dev server like from aiohttp_devtools import cli; cli().
But I've created an issue for your needs: https://github.com/aio-libs/aiohttp-devtools/issues/99

I've managed to setup debug configuration with 'Module name' instead of 'Script path' and external adev.py script:
Also, you may need to set proper 'Working directory' and PYTHONPATH (mark directories as sources roots for that).

Use Pytest with Django without using django-pytest 3rd party app

Is it possible to use Pytest with Django without using django-pytest 3rd party app?
I had tried to set this up, but kept running into random errors, like pytest couldn't find the DJANGO_SETTINGS_MODULE. Then I fixed the path, but the normal python manage.py runserver then couldn't find the DJANGO_SETTINGS_MODULE. I'm running:
Pytest 2.5.4
Python 3.4.0
Django 1.6.2
If it is possible, would you be able to provide a setup example of where to put the tests/ directory, etc... within the project so Pytest works?
Thanks

Hmm, py.test 2.5.4 does not exist afaik.
Anyway, assuming you mean to ask whether it is possible to avoid the pytest-django plugin to test Django using py.test: the short answer is no.
The long answer is yes, but it is extremely difficult to get it all to work and you will basically write at least a minimal version of pytest-django in the conftest.py file. The pytest-django plugin was created specifically to work around all the weirdness which Django does with much global state and other hidden magic.
OTOH looking at the pytest-django source would probably help you kickstart such an effort. However you may consider thinking about what it is of pytest-django you do not like and maybe file an enhancement request to improve it.

Django: Automatically executing statements in `manage.py shell`

Every time I start a shell using python manage.py shell, I want a few lines to be executed automatically. (In my case it would be a few import lines in the style of import django, my_app.)
How do I do this?

The package django-extensions does what you want. If you pip install django-extensions, and you can add the app as always (in your app list, then run syncdb), then you get a command called shell_plus.
That command loads all your models automatically if you run python manage.py shell_plus. Really handy! If you combine that the power of IPython you get a nice environment to interact with your models using the django ORM.
More information:
For the package: https://github.com/django-extensions/django-extensions
For the docs on shell_plus: http://pythonhosted.org/django-extensions/shell_plus.html
For the docs of django-extensions: http://pythonhosted.org/django-extensions/
Hope this helps. It might be less work than writing start-up scripts. As an extra django-extensions gives you great functions like graph_models (which can give you a png drawing of your database) and show_urls.

I ended up monkeypatching IPython.frontend.terminal.embed.InteractiveShellEmbed.__call__ to add the definitions I wanted. (I know many people are opposed to monkeypatching but I find it to be a good solution in this case.)

How does django-nose differ from the default Django test-runner

I've been seeing and reading about a lot of people using nose to run their Django tests. I haven't been able to figure out the added benefits of using Nose to run my Django tests. If someone could fill me in on what nose is and how it adds more to a Django project, it would be helpful.
I haven't been able to find a good document/article outlining these points.
Thank you

I was curious about this too and it seems that the main advantage of django-nose using the python nose library is "Test Discovery".
In addition, from http://readthedocs.org/docs/nose/en/latest/testing.html
you can also write simple test functions, as well as test classes that are not
subclasses of unittest.TestCase. nose also supplies a number of
helpful functions for writing timed tests, testing for exceptions, and
other common use cases. See Writing tests and Testing tools for more.
From what I understand from other python developers on freenode irc, Trial test runner on Twisted Framework have these similar features like nose.
I am still not entirely convinced about using django-nose for django development but am giving a shot and report back if I find out more!

There are a lot more features overall, but I think one major reason people use nose/djano_nose is that it allows you to very easily do code coverage.
python manage.py test myapp --with-coverage --cover-package=myapp