-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
```
What steps will reproduce the problem?
1.
Create a test.py in your application directory with the following content.
import unittest
from myapp.models import *
class MyappTestCase(unittest.TestCa…
-
```
As the summary says. We don't need to complicate gtest with Pimpl here.
```
Original issue reported on code.google.com by `w...@google.com` on 28 Jul 2010 at 6:52
-
This was a one-off script, but if this becomes something more used/usable we probably need to pour a bit of testing into it.
* [ ] create a tests directory.
* [ ] create tests for the main functio…
-
On Solaris I see the errors an the bottom of the posting.
Clearly this is because something has defined `isnan` and `isinf` to their `__builtin`-prefixed equivalents.
That "something" is the `math.h` …