[Python-modules-team] Mass filing on Python 3.7 async module import?

[Adrian Bunk]

On Sat, Jul 07, 2018 at 06:17:20PM -0400, Paul R. Tagliamonte wrote:
> Hey DPMT (BCC'ing -devel, let's keep conversaion on DPMT),
> 
> I see that Python 3.7 now raises a syntax error when you try to import
> a module that is named `async`.
> 
> ```
> $ python3.6
> Python 3.6.6 (default, Jun 27 2018, 14:44:17)
> [GCC 8.1.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import foo.async
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ModuleNotFoundError: No module named 'foo'
> >>>
> ```
> 
> With Python 3.7:
> 
> ```
> $ python3.7
> Python 3.7.0 (default, Jun 27 2018, 14:40:03)
> [GCC 8.1.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import foo.async
>   File "<stdin>", line 1
>     import foo.async
>                    ^
> SyntaxError: invalid syntax
> >>>
> ```
> 
> Quickly checking codesearch, there are a bunch of packages that have
> import lines that look like they'd fail.
> 
> Anyone mind if I do a MBF on libraries that are providing anything
> named `async.py`?

Sounds good to me.

Please make your bugs blockers of #902788, there seems to be a long 
list of Breaks required to force the correct order of package upgrades
for stretch -> buster.

>    Paul

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed