Message298450
| Author |
brett.cannon |
| Recipients |
brett.cannon, daveroundy, eric.snow, ncoghlan, pitrou |
| Date |
2017年07月16日.21:19:52 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP1=2W65c5rvSgw3nQzw-jD-Zjht-n8kVSiZM+CditMoYKZbMg@mail.gmail.com> |
| In-reply-to |
<1500207945.39.0.0423072102879.issue23916@psf.upfronthosting.co.za> |
| Content |
I agree with Antoine that this shouldn't change. Having said that, it
wouldn't be hard to write your own finder using importlib that doesn't get
the directory contents and instead checks for the file directly (and you
could even set it just for your troublesome directory to get the
performance benefit from the default finder).
On Sun, Jul 16, 2017, 05:25 Antoine Pitrou, <report@bugs.python.org> wrote:
>
> Antoine Pitrou added the comment:
>
> Thanks for the reproducer. I haven't changed my mind on the resolution,
> as it is an extremely unlikely usecase (a directory with 1e8 files is
> painful to manage with standard command-line tools). I suggest you change
> your approach, for example you could use a directory hashing scheme to
> spread the files into smaller subdirectories.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23916>
> _______________________________________
> |
|