Oh, ok. So is there a way to include data (in a package or not) in my
binary distribution?
--Mike
On Apr 30, 2008, at 9:27 AM, Phillip J. Eby wrote:
At 09:15 AM 4/30/2008 -0600, Michael Hearne wrote:
I'm having trouble bundling any kind of data (non-Python code) in
my egg.
Here are the
At 09:33 AM 4/30/2008 -0600, Michael Hearne wrote:
Oh, ok. So is there a way to include data (in a package or not) in
my binary distribution?
See the distutils docs on that. There has been some discussion
around creating a standard for including docs and other things in egg
metadata, but
Folks:
Here's an experiment you can perform. Round up a Python programmer
and ask him the following three questions:
Q1. You type import foo and it works. What kind of thing is foo?
Q2. You go to the Python package index and download something named
bar-1.0.0.tar.gz. What kind of
zooko wrote:
Folks:
Here's an experiment you can perform. Round up a Python programmer and
ask him the following three questions:
Q1. You type import foo and it works. What kind of thing is foo?
foo is a package or a module. Not enough information is provide here to
say which.
Q2.
On 10:53 pm, [EMAIL PROTECTED] wrote:
zooko wrote:
Unfortunately these answers aren't quite right. A package is
actually a directory containing an __init__.py file, and a
distribution is actually what you think of when you say package -- a
reusable package of Python code that you can, for
Nick Coghlan wrote:
zooko wrote:
Q1. You type import foo and it works. What kind of thing is foo?
foo is a package or a module. Not enough information is provide here to
say which.
Actually, it could be anything! But it's *probably* a module
(or package, but a package is also a module,
zooko [EMAIL PROTECTED] writes:
I'm willing to bet that you will get the following answers:
A1. foo [from 'import foo'] is a module.
A2. bar [of 'bar-1.2.3.tar.gz'] is a package.
A3. A distribution is a version of Linux that comes with a lot of
Free Software.
Unfortunately
