[Python-Dev] [PEP 3148] futures - execute computations asynchronously (original) (raw)
Tres Seaver tseaver at palladion.com
Fri Mar 5 21:33:25 CET 2010
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jesse Noller wrote:
On Fri, Mar 5, 2010 at 11:21 AM, Daniel Stutzbach <daniel at stutzbachenterprises.com> wrote:
On Fri, Mar 5, 2010 at 12:03 AM, Brian Quinlan <brian at sweetapp.com> wrote:
import futures +1 on the idea, -1 on the name. It's too similar to "from future import ...". Futures is a common term for this, and implemented named this in other languages. I don't think we should be adopting things that are common, and found elsewhere and then renaming them.
- -1 to the name from me as well: it isn't "scoped" properly to make it clear what the module is about. If they were inside a pacakge named 'concurrency' or some such (as hinted by Jesse Noller, I think), the clash would go away.
Tres. - --
Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkuRapAACgkQ+gerLs4ltQ7dBwCfRmMuq6X9VE8usYgSScXEA1D0 1PsAoI8MR5hjPjq9C7MFPTZhcO/T+NM4 =7wpK -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]