No idea about this issue in general, I just wanted to say: Why does modperl try to run Python code from modpython?
<*status> Unable to load modperl: Traceback (most recent call last):
<*status> File "/usr/local/lib/znc/modpython/znc.py", line 899, in get_mod_info
No idea about this issue in general, I just wanted to say: Why does modperl try to run Python code from modpython?
```
<*status> Unable to load modperl: Traceback (most recent call last):
<*status> File "/usr/local/lib/znc/modpython/znc.py", line 899, in get_mod_info
```
<!-- github-comment-id:693418927 -->
Modperl just happens to be the next module to be loaded after modpython. The issue is somewhere in `CModPython::OnModuleLoading`
This seems related to #1724
<!-- github-comment-id:693423749 -->
Modperl just happens to be the next module to be loaded after modpython.
Clarification: this is specific to modperl. Modperl has a directory in lib/znc/, and that directory is understood by updated modpython as as way to load subpackages like modperl/foo.py. Modpython sees the dir, and assumes that modperl is a python module, and tries to load it as a python module, and fails.
> Modperl just happens to be the next module to be loaded after modpython.
Clarification: this is specific to modperl. Modperl has a directory in lib/znc/, and that directory is understood by updated modpython as as way to load subpackages like `modperl/foo.py`. Modpython sees the dir, and assumes that modperl is a python module, and tries to load it as a python module, and fails.
<!-- github-comment-id:694515972 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Compiled with: ./configure.sh --enable-debug --enable-ipv6 --enable-openssl --enable-zlib --enable-perl --enable-swig --enable-cyrus --enable-charset --disable-tcl --enable-i18n --enable-python
This is perl 5, version 18, subversion 2 (v5.18.2) built for x86_64-linux-gnu-thread-multi, Python 3.4.3
No idea about this issue in general, I just wanted to say: Why does modperl try to run Python code from modpython?
Modperl just happens to be the next module to be loaded after modpython. The issue is somewhere in
CModPython::OnModuleLoadingThis seems related to #1724
Clarification: this is specific to modperl. Modperl has a directory in lib/znc/, and that directory is understood by updated modpython as as way to load subpackages like
modperl/foo.py. Modpython sees the dir, and assumes that modperl is a python module, and tries to load it as a python module, and fails.