On 13-dec-2005, at 22:42, M.-A. Lemburg wrote:
> Bob Ippolito wrote:
>> On Dec 13, 2005, at 11:13 AM, M.-A. Lemburg wrote:
>> I'd like to focus attention on these distribution formats
>> that distutils is missing:
>>
>
> I'd like to another important candidate to the list:
>>>
I've taken to heart your suggestions. The result is what I hope is a
very simple example / tutorial that demonstrates:
* the file structure of a project destined to be an egg
* how to use doctests and unit tests with setuptools / eggs
* how to build and deploy an egg
* how to register with p
On Wed, 14 Dec 2005, Todd Greenwood-Geer wrote:
[...]
> Anyone have any good naming conventions for module tests?
>
> [module name]_unittest.py
> test_[module_name].py
> unittest_[module_name].py
Hmm, I actually misread your question in your original email...
Python itself uses test_[module_name
Setuptools in SVN now provides preliminary support for installing eggs in
.egg-info directory style, so that setuptools-based projects can be wrapped
by system packagers who wish to avoid using .egg files or directories. In
addition, you can now use setuptools to install non-setuptools packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great. The pbu utility is perfect. Thanks, yet again.
Phillip J. Eby wrote:
| At 12:59 PM 12/14/2005 -0800, Todd Greenwood-Geer wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> PROBLEM:
|> I would like to be able to execute the egg bui
At 07:02 PM 12/11/2005 -0800, Bob Ippolito wrote:
>It looks like easy_install can't do this yet.
And it's not going to be able to. The closest thing I can envision is that
if you have a master project with a setup.py that runs each child project's
setup.py (or just a setup() call), such that ea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok. I'll fall back to copying the file in the offline scenario. Thanks.
Phillip J. Eby wrote:
| At 10:32 AM 12/14/2005 -0800, Todd Greenwood-Geer wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> I'm finding that I'm coding online and o
(Disclaimer: this email does not advocate using eggs; it's a comment on
needed functionality in bdist_mpkg, however it gets implemented.)
At 02:49 PM 12/14/2005 +0100, M.-A. Lemburg wrote:
> > I have definitely had real-world experience where bdist_mpkg fails
> > miserably. The worst cases are
At 10:18 AM 12/14/2005 -0800, Todd Greenwood-Geer wrote:
>test_[module_name].py
This is a common convention used by large Python projects. Other
conventions include test/foo.py and tests/bar.py.
>Then there's the issue of differentiating unit tests from functional
>tests, scenario tests...
I
At 10:32 AM 12/14/2005 -0800, Todd Greenwood-Geer wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>I'm finding that I'm coding online and offline. When I'm offline, I
>would really like to use the svn:externals definition for ez_setup. It
>seems that the best way to do this would be to cre
At 12:59 PM 12/14/2005 -0800, Todd Greenwood-Geer wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>PROBLEM:
>I would like to be able to execute the egg build from several
>directories, like so:
>
>$ cd active/SimpleExampleEgg
>$ python setup.py bdist_egg
>
>then, at other times, i'd like t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PROBLEM:
I would like to be able to execute the egg build from several
directories, like so:
$ cd active/SimpleExampleEgg
$ python setup.py bdist_egg
then, at other times, i'd like to change to a package directory and
execute the builds from there:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm finding that I'm coding online and offline. When I'm offline, I
would really like to use the svn:externals definition for ez_setup. It
seems that the best way to do this would be to create a 'peak' project
just for the ez_setup files. Then, when I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To the list :
Anyone have any good naming conventions for module tests?
[module name]_unittest.py
test_[module_name].py
unittest_[module_name].py
Then there's the issue of differentiating unit tests from functional
tests, scenario tests...
Here's m
Bob Ippolito wrote:
> On Dec 13, 2005, at 1:42 PM, M.-A. Lemburg wrote:
>
>> Bob Ippolito wrote:
>>> On Dec 13, 2005, at 11:13 AM, M.-A. Lemburg wrote:
>> I'd like to another important candidate to the list:
>>
>> bdist_mpkg:
>>Mac OS X installer format
>>Part of py2app
Bernhard Herzog wrote:
> "M.-A. Lemburg" <[EMAIL PROTECTED]> writes:
>
>>> What do you have in mind - a bdist_wininst lookalike for
>>> Python packages, built with inno?
>> Yes. One that creates an Inno setup file and then compiles
>> everything into an installer using the Inno, but installing
>>
Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>> Would any of the authors (I've tried to CC them) be willing to
>> contribute their distutils command to the PSF for integration ?
>
> I was hoping to contribute bdist_msi before 2.5. Before that, I need
> atleast two more releases; I have some feedb
17 matches
Mail list logo
