certifi==2020.6.20,chardet==3.0.4,colorama==0.4.3,future==0.18.2,idna==2.10,mando==0.6.4,PyYAML==5.3.1,radon==4.3.1,requests==2.24.0,six==1.15.0,urllib3==1.25.10,xenon==0.7.0

Traceback (most recent call last):
  File "/home/proofit404/data/generics/.tox/xenon/bin/xenon", line 8, in <module>
    sys.exit(main())
  File "/home/proofit404/data/generics/.tox/xenon/lib/python3.8/site-packages/xenon/__init__.py", line 72, in main
    from xenon.core import analyze
  File "/home/proofit404/data/generics/.tox/xenon/lib/python3.8/site-packages/xenon/core.py", line 5, in <module>
    from radon.complexity import cc_rank, SCORE
  File "/home/proofit404/data/generics/.tox/xenon/lib/python3.8/site-packages/radon/complexity.py", line 7, in <module>
    from flake8_polyfill import options
ModuleNotFoundError: No module named 'flake8_polyfill'

Maybe its a radon issue, but I've got the error when installing xenon tool.

I wanted to be able to run this xenon code --max-average A --max-modules C --max-absolute D --max-average-num 2.3

While this new argument is similar to max-average, it let's you threshold to a more specific value while you're still improving the code's complexity.

Hi! Thanks for this awesome package.

I guess that user-base can be extended if you create a flake8 plugin for xenon. So, here's how the final usage will look like:

1. pip install flake8 xenon
2. flake8 . (runs both flake8 and xenon)

This dependency is out of date and is breaking something on my side which is not directly linked to xenon. Whole story below.

My CI pipeline recently broke with the following exception:

+flake8 --ignore E501,F403,F401,F405 src
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.4.2/bin/flake8", line 11, in <module>
    sys.exit(main())
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/main/cli.py", line 16, in main
    app.run(argv)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/main/application.py", line 316, in run
    self._run(argv)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/main/application.py", line 299, in _run
    self.initialize(argv)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/main/application.py", line 290, in initialize
    self.register_plugin_options()
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/main/application.py", line 150, in register_plugin_options
    self.check_plugins.register_options(self.option_manager)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/plugins/manager.py", line 457, in register_options
    list(self.manager.map(register_and_enable))
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/plugins/manager.py", line 267, in map
    yield func(self.plugins[name], *args, **kwargs)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/plugins/manager.py", line 453, in register_and_enable
    call_register_options(plugin)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/plugins/manager.py", line 363, in generated_function
    return method(optmanager, *args, **kwargs)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/flake8/plugins/manager.py", line 213, in register_options
    add_options(optmanager)
  File "/home/travis/virtualenv/python3.4.2/lib/python3.4/site-packages/radon/complexity.py", line 132, in add_options
    parser.config_options.append('radon-max-cc')
AttributeError: 'OptionManager' object has no attribute 'config_options'

This issue is unrelated to xenon but as I install xenon along with flake8, the installed version of radon is currently the 1.4.0. To work properly, flake8 needs the 1.4.2 version.

I understand this issue is completely out of scope of this project but I would like to spot the fact that the installed dependency is out of date and that this update would cause no harm to xenon while enabling it to be used more smoothly along with other widely-deployed tools such as flake8.

On installing xenon via pip install xenon, yaml dependency is missing. Additionally, one cannot simply pip install yaml, so I'm not sure about wich implementation of yaml was used.

Hi,

I see that this has come up in the past and I was hoping it would be possible to again update the PyYAML dependency. My project depends on PyYAML version 6 and xenon is <6.0.

Using version ^0.8.0 for xenon

Updating dependencies
Resolving dependencies... (3.8s)

  SolverProblemError

  Because no versions of xenon match >0.8.0,<0.9.0
   and xenon (0.8.0) depends on PyYAML (>=4.2b1,<6.0), xenon (>=0.8.0,<0.9.0) requires PyYAML (>=4.2b1,<6.0).
  So, because x-service depends on both PyYAML (6.0) and xenon (^0.8.0), version solving failed.

Thanks

Many libraries such as radon allow for modules to be executed via python -m.

This change allows for python -m xenon to work. This allows for CI or local machines that have multiple versions of python to execute xenon and know exactly which interpreter is being invoked.

While working on a project that uses secure version of pyyaml I have failed to install xenon with poetry, because these packages rely on different library versions:

Because no versions of layer-linter match >0.12.0,<0.13.0
 and layer-linter (0.12.0) depends on PyYAML (>=4.2b1,<5.0.0), layer-linter (>=0.1
2.0,<0.13.0) requires PyYAML (>=4.2b1,<5.0.0).
Thus, layer-linter (>=0.12.0,<0.13.0) is incompatible with xenon (>=0.5,<0.6).
So, because kira depends on both xenon (^0.5) and layer-linter (^0.12.0), version
solving failed.

Steps:

1. poetry init - to create a new project
2. poetry add xenon
3. poetry add layer-lint

Running xenon (version 0.5.1 or 0.5.2 with mando-0.3.3 and radon-1.4.2) on our code base (Python 2.7) works as expected. But as of very recently, the latest dependencies (mando-0.6.4 and radon-2.0.3) are causing weird warnings of this form:

WARNING:xenon:cannot parse path/to/source.py: invalid syntax (<unknown>, line 1)

There is nothing wrong with those (dozens of) files. Downgrading to radon-1.4.2 gets rid of the warnings.

Not a critical issue, but figured worth opening a ticket for :slightly_smiling_face: Thanks!

PS1. I just confirmed that radon-2.0.2 works. The issue was introduced in radon-2.0.3 :information_source: PS2. Oops, looks like there was already a ticket in radon's issue tracker: https://github.com/rubik/radon/issues/133

PyYAML 3.11 fails compilation during pip install. If xenon allowed PyYaml 3.12, which added Windows wheels for Py27, 34, and 35, then Windows users would be super happy :-)

I can't seem to get xenon to install with a simple pip install. I tried with a python setup.py install as well and got the same result. It looks like the README.rst isn't included in the distribution on pypi.

[josh@jh-mbp tmp]$ virtualenv xenonradon
New python executable in xenonradon/bin/python
Installing Setuptools..............................................................................................................................................................................................................................done.
Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.
[josh@jh-mbp tmp]$ cd xenonradon/
[josh@jh-mbp xenonradon]$ source bin/activate
(xenonradon)[josh@jh-mbp xenonradon]$ php install radon
Could not open input file: install
(xenonradon)[josh@jh-mbp xenonradon]$ pip install radon
Downloading/unpacking radon
  Downloading radon-0.5.1.tar.gz (224kB): 224kB downloaded
  Running setup.py egg_info for package radon

Downloading/unpacking mando (from radon)
  Downloading mando-0.3.1.tar.gz
  Running setup.py egg_info for package mando

Downloading/unpacking colorama (from radon)
  Downloading colorama-0.3.1.tar.gz
  Running setup.py egg_info for package colorama

Downloading/unpacking pathfinder (from radon)
  Downloading pathfinder-0.5.3.tar.gz
  Running setup.py egg_info for package pathfinder

Installing collected packages: radon, mando, colorama, pathfinder
  Running setup.py install for radon

    Installing radon script to /private/tmp/xenonradon/bin
  Running setup.py install for mando

  Running setup.py install for colorama

  Running setup.py install for pathfinder

Successfully installed radon mando colorama pathfinder
Cleaning up...
(xenonradon)[josh@jh-mbp xenonradon]$ pip install xenon
Downloading/unpacking xenon
  Downloading xenon-0.1.tar.gz
  Running setup.py egg_info for package xenon
    Traceback (most recent call last):
      File "<string>", line 16, in <module>
      File "/private/tmp/xenonradon/build/xenon/setup.py", line 6, in <module>
        with open(os.path.join(os.path.dirname(__file__), 'README.rst')) as fobj:
    IOError: [Errno 2] No such file or directory: '/private/tmp/xenonradon/build/xenon/README.rst'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 16, in <module>

  File "/private/tmp/xenonradon/build/xenon/setup.py", line 6, in <module>

    with open(os.path.join(os.path.dirname(__file__), 'README.rst')) as fobj:

IOError: [Errno 2] No such file or directory: '/private/tmp/xenonradon/build/xenon/README.rst'

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /private/tmp/xenonradon/build/xenon
Storing complete log in /Users/josh/.pip/pip.log

Skip the level and module name to have log line starting with message. This option affects also how the "block" and "module" violations are printed - the path is in the front of the message. When using xenon in PyCharm terminal, one can benefit from PyCharm changing the path to the violation location into the active link.

For more details see Feature Request #49

The PyCharm terminal has a feature that if the line starts with the path to the file and code line, it is replaced with a link, and when clicked, the user is moved to that location. This property of the terminal is very useful when using various linters that return the location of violation of some rules.

Would it be possible to e.g. add an option that will change the default log format to one without log level, module and change the log message format - remove quotes around the path?

CURRENT:

ERROR:xenon:block "jaba/core/engine.py:53 get_info" has a rank of C
ERROR:xenon:block "jaba/scripts/monitor.py:26 display_dashboard" has a rank of C

(desired) PyCharm Friendly:

jaba/core/engine.py:53 get_info has a rank of C
jaba/scripts/monitor.py:26 display_dashboard has a rank of C

The problem is that xenon with "long options" (--max-absolute B, --max-modules B, --max-average A) does not find issues with complexity when used as pre-commit hook. When used with "short options" ( -bB, -mB, -aA) - it finds the issues with too complex code.

Here is my xenon hook definition in .pre-commit-config.yaml:

    # monitor code complexity
    -   repo: https://github.com/rubik/xenon
        rev: v0.9.0
        hooks:
            -   id: xenon
                args: [ --max-absolute B, --max-modules B, --max-average A ]
               #  args: [ -bB, -mB, -aA ]

I was running it on macOS.

I want to use xenon to prevent developers in my organization from adding new bad blocks, but still don't fail for existing bad blocks. Ignore/Exclude only allows to exclude by module, this isn't specific enough for us.

My list of ignore and exclude options grew quite big, together with --max-absolute B --max-modules A --max-average A it looks to verbose to use.

Is it an option to specify the configuration inside setup.cfg (default place for configuring python tools like flake8, mypy, isort, etc)?