>The above is an indication that your source code isn't being
>found. My guess is that since you're saying you want to install a
>"script" but can't import it, what you actually have is a standalone
>*module*, not a script or a package. find_packages() cannot find
>such modules, you must lis
At 10:21 AM 1/10/2009 -0800, rayterrill wrote:
They're going to be distributed to over 800+ locations
internally, so I was looking for a repeatable structured mechanism to deploy
the code and verify that it was installed correctly, vs. just copying the
files into the python sys.path and hoping th
>The above is an indication that your source code isn't being
>found. My guess is that since you're saying you want to install a
>"script" but can't import it, what you actually have is a standalone
>*module*, not a script or a package. find_packages() cannot find
>such modules, you must lis
At 03:03 PM 1/9/2009 -0600, ray terrill wrote:
I'm using python2.4 to try to package and deliver a custom python
script. I'm unable to import the package.
My setup.py looks like the following:
from setuptools import setup, find_packages
setup(
name = "randomscript",
version = "1.0",
p
On Fri, Jan 09, 2009 at 03:03:08PM -0600, ray terrill wrote:
> I'm using python2.4 to try to package and deliver a custom python script.
> I'm unable to import the package.
>
> My setup.py looks like the following:
> from setuptools import setup, find_packages
> setup(
>name = "randomscript",
I'm using python2.4 to try to package and deliver a custom python script.
I'm unable to import the package.
My setup.py looks like the following:
from setuptools import setup, find_packages
setup(
name = "randomscript",
version = "1.0",
packages = find_packages(),
)
I'm building the pack
