New submission from Danilo Bargen :
Most assert statements of the unittest module provide both an assert statement
as well as its inverse, like "assertIn" and "assertNotIn". There is apparently
no such thing for exceptions.
I can do the following:
> with self.ass
Danilo Bargen added the comment:
>> I don't want to simply execute the code and hope that it doesn't raise
>> an exception, because if it does, the test fails with an "error" status
>> instead of a "failed" status.
>
> So what?
A buggy t
Danilo Bargen added the comment:
I disagree, I think this bug should be reopened and fixed.
A use case that I just ran into: I'm using a Django form with time fields that
aren't required, but that are only valid in combination (if there's a open time
there has to be a close tim
Changes by Danilo Bargen :
--
nosy: +gwrtheyrn
___
Python tracker
<http://bugs.python.org/issue16791>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Danilo Bargen :
--
nosy: +gwrtheyrn
___
Python tracker
<http://bugs.python.org/issue7434>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Danilo Bargen:
Where I work, we use a custom pypi server to upload our internal packages.
With a package that has a setup.py created using setuptools, I can simply issue:
$ python setup.py sdist register upload -r local
...and it will get registered and uploaded to our
Danilo Bargen added the comment:
chris, no, that command registers the package with the local index but tries to
upload it to pypi.
What works is "setup.py sdist register -r wbrp upload -r wbrp" but that's kind
of awful.
--
___
