[issue27383] executuable in distutils triggering microsoft anti virus

2016-06-28 Thread Rob Bairos
Rob Bairos added the comment: Great. Thanks for the update On Tue, Jun 28, 2016 at 2:37 PM, Steve Dower <rep...@bugs.python.org> wrote: > > Steve Dower added the comment: > > FYI the definitions have been updated and I'm no longer seeing the false > positive. &

[issue27383] executuable in distutils triggering microsoft anti virus

2016-06-24 Thread Rob Bairos
Rob Bairos added the comment: thanks for the quick action! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27383> ___ ___ Pyth

[issue27383] executuable in distutils triggering microsoft anti virus

2016-06-24 Thread Rob Bairos
New submission from Rob Bairos: python 3.5: wininst-14.0.exe Is triggering Microsoft Security Essentials virus detection: Recommended action: Remove this software immediately. Items: file:D:\PythonBuilds\202ee57ca3\py\Lib\distutils\command\wininst-14.0.exe I've tried on two separate

[issue18812] PyImport_Import redundant calls to find module

2013-08-26 Thread Rob Bairos
Rob Bairos added the comment: Okay, thanks for looking into it. Cheers -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18812 ___ ___ Python-bugs

[issue18812] PyImport_Import redundant calls to find module

2013-08-23 Thread Rob Bairos
Rob Bairos added the comment: However, if it fails __import()__ it doesn't get to the sys.modules[] call anyways. The only case affected by this are: PASS the __import()__ call, then FAIL the sys.modules[] lookup afterwards. Why will that effect anything currently out

[issue18812] PyImport_Import redundant calls to find module

2013-08-22 Thread Rob Bairos
New submission from Rob Bairos: Why does PyImport_Import (import.c) call __import__ then immediately discard the result, and then look for the module again in the module dictionary? It will return the same value in both cases no? Ive included the relevant portion of the code below. Its

[issue18812] PyImport_Import redundant calls to find module

2013-08-22 Thread Rob Bairos
Changes by Rob Bairos rbai...@gmail.com: -- type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18812 ___ ___ Python-bugs-list mailing

[issue13314] ImportError ImportError: Import by filename, should be deferred until sys.meta_path hooks are processed

2011-11-04 Thread Rob Bairos
Rob Bairos rbai...@gmail.com added the comment: Yah, thinking about this further, the real error is that sys.meta_path allows processing of names with #,?* etc. I can see why this would cause problems, as python names must only be _ and alphanumeric characters. I'll re-implement this. Thanks

[issue13314] ImportError ImportError: Import by filename, should be deferred until sys.meta_path hooks are processed

2011-11-03 Thread Rob Bairos
Rob Bairos rbai...@gmail.com added the comment: Why is a module name syntactically improper simply because it contains a slash? That seems an arbitrary definition, that serves no purpose, except to discourage accidentally specifying a filename. Module with unusual characters all reach

[issue13314] ImportError ImportError: Import by filename, should be deferred until sys.meta_path hooks are processed

2011-11-01 Thread Rob Bairos
New submission from Rob Bairos rbai...@gmail.com: When adding hooks to sys.meta_path, to correctly deal with arbitrarily named non-disk module definitions, module names with slashes should still be processed. As it stands when executing statements such as: import my_module_123#/123 or even

[issue13314] ImportError ImportError: Import by filename, should be deferred until sys.meta_path hooks are processed

2011-11-01 Thread Rob Bairos
Changes by Rob Bairos rbai...@gmail.com: -- type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13314 ___ ___ Python-bugs-list mailing