On Sat, Sep 29, 2018 at 8:18 AM Antoine Pitrou <solipsis at pitrou.net> wrote: > On Sat, 29 Sep 2018 08:13:19 -0400 > Sean Harrington <seanharr11 at gmail.com> wrote: > > > > > > Hmm... We might have a disagreement on the target audience of the > > > multiprocessing module. multiprocessing isn't very high-level, I would > > > expect it to be used by experienced programmers who know how to mutate > > > a global variable from a lexical scope. > > > > > > > >>> It is one thing to MUTATE a global from a lexical scope. No gripes > > there. The specific concept I'm referencing here, is "DECLARING a global > > variable, from within a lexical scope". This is not as a intuitive for > most > > programmers. > > Well, you don't have to. You can bind it to None in the top-level > scope and then mutate it from the lexical scope: > > my_resource = None > > def do_work(): > global my_resource > my_resource = ... > > >>> Yes but this is even more constraining, as it forces the parent process to declare a global variable that it likely never uses! > Regards > > Antoine. > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/seanharr11%40gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180929/106083bb/attachment-0001.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4