On Sep 8, 2010, at 12:56 PM, P.J. Eby wrote:
> At 12:00 PM 9/8/2010 -0400, Doug Hellmann wrote:
>> Instead of explicitly listing packages, I use find_package_data() and then
>> get the package names from that result. The odd thing is I get a package
>> "PyMOTW.ElementTree" but not "PyMOTW.xml.
On Sep 8, 2010, at 12:56 PM, P.J. Eby wrote:
> At 12:00 PM 9/8/2010 -0400, Doug Hellmann wrote:
>> Instead of explicitly listing packages, I use find_package_data() and then
>> get the package names from that result. The odd thing is I get a package
>> "PyMOTW.ElementTree" but not "PyMOTW.xml.
At 12:00 PM 9/8/2010 -0400, Doug Hellmann wrote:
Instead of explicitly listing packages, I use find_package_data()
and then get the package names from that result. The odd thing is I
get a package "PyMOTW.ElementTree" but not
"PyMOTW.xml.etree.ElementTree". Maybe I'm misunderstanding/misusing
On Sep 8, 2010, at 7:37 AM, Eric Smith wrote:
> On 9/8/10 7:34 AM, Doug Hellmann wrote:
>> I'm having some problems creating an sdist for a nested package where some
>> of the levels only include __init__.py and the subdirectories. The full
>> list of files is fairly long, but here's a snippet
On 9/8/10 7:34 AM, Doug Hellmann wrote:
I'm having some problems creating an sdist for a nested package where some of
the levels only include __init__.py and the subdirectories. The full list of
files is fairly long, but here's a snippet to give you an idea of the layout
for the inputs:
Forgot to include version info:
Python 2.7
distribute 0.6.10
Paver 1.0.3
Doug
On Sep 8, 2010, at 7:34 AM, Doug Hellmann wrote:
> I'm having some problems creating an sdist for a nested package where some of
> the levels only include __init__.py and the subdirectories. The full list of
> file
