[Python-Dev] draft PEP: virtual environments

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/30/2011 08:35 AM, Vinay Sajip wrote:
> Antoine Pitrou <solipsis <at> pitrou.net> writes:
> 
>> We already have Unix shell scripts and BAT files in the source
>> tree.
> 
> Do we have a blessed location in the stdlib for data files in
> general? Although we're talking in this instance about scripts,
> they're just data as far as the venv module is concerned. While
> it's not uncommon for data which is included with packages to be
> installed in the source tree for that package(e.g. packaging's test
> data), I'm not sure what one would do with data which belongs to a
> top-level module. At the moment it's in the source as a
> base64-encoded string, but I'm not sure that's ideal - it's
> workable only because the data is so small. I don't really want to
> add a Lib/scripts.zip adjacent to venv.py, which venv accesses via
> os.path.dirname(__file__), because if every module did this, it
> would be a tad untidy.
> 
> The other alternative would be to make venv a package with all its
> code in venv/__init__.py and a scripts.zip adjacent to that. Does
> that seem like a better solution? Can anyone suggest better
> alternatives? Sorry if this has come up before and I've missed
> something obvious.

+1 to making it a package and keeping the data in the package.

- -1 to a zip file:  each scripts should be a noraml, version-controlled
entity.



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.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6tb+8ACgkQ+gerLs4ltQ463wCfZoOOYK1c7XgAaihSdM9+0dxn
/YgAoMVlq+ZRGA6xZUFNrajSbdr4aUQZ
=P6zT
-----END PGP SIGNATURE-----