| Summary: | dev-python/django-9999 incompatible with postgresql on freebsd | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | michael <michael> |
| Component: | FreeBSD | Assignee: | Gentoo/BSD Team <bsd+disabled> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | bugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | FreeBSD | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
michael@smith-li.com
2008-08-31 23:34:17 UTC
A (not perfect but) slightly better option, emerge postgres without python useflag. That way you can have threaded python, and for django just use psycopg2. Not sure but I think this will get solved once fbsd7 gets in. > A (not perfect but) slightly better option, emerge postgres without python
> useflag. That way you can have threaded python, and for django just use
> psycopg2.
> Not sure but I think this will get solved once fbsd7 gets in.
>
Now that fbsd7 (and 8) is out, is this still applicable?
The PostgreSQL ebuilds don't require Python to be built with threads. The upstream documentation doesn't mention anything about threads either. Is this still an issue, or is it really fixed? |