BlueBird <[EMAIL PROTECTED]> wrote:
> On Dec 2, 4:27 pm, BlueBird <[EMAIL PROTECTED]> wrote:
>> On Nov 26, 5:07 pm, "Sergio Correia" <[EMAIL PROTECTED]> wrote:
>>
>> >Bluebird:
>>
>> > If you are using python 2.5, relative imports are no longer an
>> > issue:http://docs.python.org/whatsnew/pep-328.
On Dec 2, 4:27 pm, BlueBird <[EMAIL PROTECTED]> wrote:
> On Nov 26, 5:07 pm, "Sergio Correia" <[EMAIL PROTECTED]> wrote:
>
> >Bluebird:
>
> > If you are using python 2.5, relative imports are no longer an
> > issue:http://docs.python.org/whatsnew/pep-328.html
>
> It does not solve my problem, or I
On Nov 26, 5:07 pm, "Sergio Correia" <[EMAIL PROTECTED]> wrote:
> Bluebird:
>
> If you are using python 2.5, relative imports are no longer an
> issue:http://docs.python.org/whatsnew/pep-328.html
It does not solve my problem, or I missed something:
[EMAIL PROTECTED] /cygdrive/d/work/work/vy-dev/f
On Nov 20, 4:09 pm, Jens <[EMAIL PROTECTED]> wrote:
>
> 1) Should I put my unittests in a subdirectory? Does the subdirectory
> have to be a package?
As others have suggested, this is a good way to organise your tests.
To avoid problems with the import path, look at nosetests [1]. This
allows you
Bluebird:
If you are using python 2.5, relative imports are no longer an issue:
http://docs.python.org/whatsnew/pep-328.html
That problem solved, what you sometimes want is to change the version
of your package. I just change the text in the PTH file, to point to
another version, and voilá (no ne
On 2007-11-24, BlueBird <[EMAIL PROTECTED]> wrote:
> On Nov 21, 7:05 am, "Sergio Correia" <[EMAIL PROTECTED]> wrote:
> And then you do your development in python-dev. But how do you manage
> multiple development branches of the same program ?
If you are using SVN, you may want to check out 'combi
On Nov 21, 7:05 am, "Sergio Correia" <[EMAIL PROTECTED]> wrote:
> As a side note, I find much easier to drop a PTH file than messing
> with pythonpath. If you are not familiar with PTH files, what I do is
> this
>
> 1) Go to "C:\Program Files\Python25\Lib\site-packages" or whatever is
> appropiate
On 21 Nov., 05:34, Ben Finney <[EMAIL PROTECTED]>
wrote:
>
> I hope the above makes it clearer what I prefer for this situation.
>
It does. You've been most helpful - thanks a lot! I'll bookmark this
thread and keep it under my pillow :-)
--
http://mail.python.org/mailman/listinfo/python-list
As a side note, I find much easier to drop a PTH file than messing
with pythonpath. If you are not familiar with PTH files, what I do is
this
1) Go to "C:\Program Files\Python25\Lib\site-packages" or whatever is
appropiate in your case.
2) Create a text file, name it something like "MyProjects.PTH
Jens <[EMAIL PROTECTED]> writes:
> On 21 Nov., 04:16, Jens <[EMAIL PROTECTED]> wrote:
> > On 21 Nov., 01:46, [EMAIL PROTECTED] wrote:
> > dummy/
> > dummy_package/
> > __init__.py
> > moduleA.py
> > tests/
> >__init__.py
> >test.py
To avoid confusion, the directory t
On 21 Nov., 04:16, Jens <[EMAIL PROTECTED]> wrote:
> On 21 Nov., 01:46, [EMAIL PROTECTED] wrote:
>
>
>
> > On Nov 20, 4:09 pm, Jens <[EMAIL PROTECTED]> wrote:
>
> > > Dear Reader,
>
> > > I'm writing some modules in Python, and I'm also using unittests. I'm
> > > wondering about some things:
>
> >
On 21 Nov., 01:46, [EMAIL PROTECTED] wrote:
> On Nov 20, 4:09 pm, Jens <[EMAIL PROTECTED]> wrote:
>
> > Dear Reader,
>
> > I'm writing some modules in Python, and I'm also using unittests. I'm
> > wondering about some things:
>
> I'd love to hear how others manage this sort of thing as well. I'll
Jens <[EMAIL PROTECTED]> writes:
> 1) Should I put my unittests in a subdirectory?
I find that it is best to do so even for single-module packages,
because it makes writing the 'setup.py' easier ("don't install
anything in the unit test directory").
> Does the subdirectory have to be a package?
Let's see:
> 1) Should I put my unittests in a subdirectory? Does the subdirectory
> have to be a package?
Sure, to avoid cluttering put the tests in a folder called 'tests'
(and any input the tests require, like mock files, output files used
to test if the output is correct, etc etc, should be p
On Nov 20, 4:09 pm, Jens <[EMAIL PROTECTED]> wrote:
> Dear Reader,
>
> I'm writing some modules in Python, and I'm also using unittests. I'm
> wondering about some things:
I'd love to hear how others manage this sort of thing as well. I'll
describe what I've found works best for me, and if others
15 matches
Mail list logo
