I’m sorry to keep scratching this, but for completeness and so that I can
assure myself that pros and cons have all been accounted for, I took a
moment to “weigh” future in terms of disk-size, file and line count.
On it’s own, future and all that it is, weighs in at..
- 1.78MiB
- 228 individual Python modules
- 43977 lines
Whereas six.py is a single file, 31kb at 869 lines.
Here’s how I did my measurements.
*Module count*
>
$ pip install future --target .
Collecting future
Installing collected packages: future
Successfully installed future-0.16.0
$ python
...>>> import os>>> modulecount = 0>>> for base, dirs, files in
os.walk("."):... for file in files:... if file.endswith(".py"): #
Excluding .pyc files... modulecount += 1
...>>> modulecount228
*Line count*
>>> linecount = 0>>> for base, dirs, files in os.walk("."):... for file in
>>> files:... abspath = os.path.join(base, file)... with open(abspath)
>>> as f:... linecount += len(f.readlines())
...>>> linecount43977
>>>
With this in mind, I can see the lure and advantage of Python 3 syntax, but
at the expense of “translating on install”, not being able to use pyglet as
a vendor package and adding over 40,000 lines of code to the existing
104,000 lines of code in pyglet today, are you sure it’s worth it?
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
