A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-October/122356.html below:

[Python-Dev] PEP 427: data directory

[Python-Dev] PEP 427: data directoryAntoine Pitrou solipsis at pitrou.net
Mon Oct 22 22:28:39 CEST 2012
On Mon, 22 Oct 2012 16:26:57 -0400
Daniel Holth <dholth at gmail.com> wrote:
> On Mon, Oct 22, 2012 at 4:20 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> >
> > Hello,
> >
> > The FAQ has this weird statement:
> >
> > “This specification does not have an opinion on how you should organize
> > your code. The .data directory is just a place for any files that are
> > not normally installed inside site-packages or on the PYTHONPATH.”
> >
> > But, say, if I want to install some init script to /etc/init.d by using
> > distutils' data_files argument:
> >
> > setup.py(...,
> >     data_files=[('/etc/init.d', ['my-init-script'])]
> >     )
> >
> > How is it stored and represented by the wheel format?
> >
> > Regards
> >
> > Antoine.
> 
> Distutils' "data" category in a wheel package-1.0.data/data/ directory
> usually maps to / (or the root of the virtualenv). Your init script
> would probably wind up in there.

Ok, thanks. Might be nice to add as a FAQ entry :-)

Regards

Antoine.
More information about the Python-Dev mailing list

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