# Why does \`from module import\` support \`(module, module)\`, but not merely \`import\`?

**URL:** <https://discuss.python.org/t/why-does-from-module-import-support-module-module-but-not-merely-import/91622>\
**Category:** Python Help\
**Created:** [May 11, 2025, 6:41pm UTC](https://discuss.python.org/t/why-does-from-module-import-support-module-module-but-not-merely-import/91622 "2025-05-11T18:41:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Stefan2](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stefan2/32/18492_2.png) [@Stefan2](https://discuss.python.org/u/Stefan2)\
**Post date:** [May 11, 2025, 7:44pm UTC](https://discuss.python.org/t/why-does-from-module-import-support-module-module-but-not-merely-import/91622/2 "2025-05-11T19:44:55Z")

</div>

There are some arguments under this recent proposal to support this:

> [@Allow import (some,list,of,modules,with,parenthesis)](https://discuss.python.org/t/allow-import-some-list-of-modules-with-parenthesis/77001):
>
> Basically, I think the import statement ought to accept parenthesis, just as “from blah import (a,b,c)” does. Ie this code, which is currently a syntax error: import (os, sys, ... importlib) ought to be accepted and be equivalent to import os, sys, ..., importlib Currently, the workaround is to simply break this up into separate import statements, but I don’t see any benefit to forcing that split and the inconsistency with “from blah import (a,b,c)” is awkward and surprising imo. (I…

---

_[View the full topic](https://discuss.python.org/t/why-does-from-module-import-support-module-module-but-not-merely-import/91622)._