Tried homebrew - this was a response to another reply Thomas.
brew update
Here I tried:
brew install postgresql
but had this error Error: Failed executing: make install-world
(postgresql.rb:67)
So instead I did this:
brew install postgres --no-ossp-uuid --no-python --no-rubie
Then when
On 6/16/12 9:41 PM, Moshe Voloshin wrote:
I tried that too, but it didn't change anythin
Tried what too? I've had good luck with python, virtualenv, and
postgresql from MacPorts and then using virtualenv and pip to get
psycopg2, django, etc.
The library path from your error indicates that you
I tried that too, but it didn't change anythin
On Saturday, June 16, 2012 9:21:38 PM UTC-7, Kurtis wrote:
>
> Try using the Brew (or ports or whatever it's called on Mac) system to
> install Python, PostgreSQL, and the postgresql development libs.
>
> On Sat, Jun 16, 2012 at 11:22 PM, Moshe Volos
Try using the Brew (or ports or whatever it's called on Mac) system to
install Python, PostgreSQL, and the postgresql development libs.
On Sat, Jun 16, 2012 at 11:22 PM, Moshe Voloshin wrote:
> Replying to this old post as I am having this problem of:
> Symbol not found: _PQbackendPID
> On MAC OS
Replying to this old post as I am having this problem of:
Symbol not found: _PQbackendPID
On MAC OS x 10.6.8
using:
python 2.7 and postgres 9.1.4
On virtual env
Wanted to ask if you guys seen this issue with python 2.7 and do you know
if there is a solution to this.
Thanks
On Sunday, July 18, 20
thanks Andrew,
Now I've installed Pinax into a Virtualenv and it's working fine...I
installed only the libs versions that Pinax script install.
On Sat, Aug 21, 2010 at 10:55 PM, AndrewK wrote:
> I've had the same problem on my Mac just now.
> It seems like this is an issue with django-timezones
I've had the same problem on my Mac just now.
It seems like this is an issue with django-timezones
Try to install dev version from here:
pip install -e
git://github.com/brosner/django-timezones.git#egg=django-timezones
Andrew
On Aug 9, 1:40 pm, Daniel França wrote:
> Thanx for all the help,
>
thanx, I'll look at that =)
On Tue, Aug 10, 2010 at 12:31 PM, Xavier Ordoquy wrote:
> It is a bit trickier.
> Pinax application gets all their dependancies through pip installation and
> requirement files.
> If you have a pinax application, take a look in the requirements directory.
> You'll find
It is a bit trickier.
Pinax application gets all their dependancies through pip installation and
requirement files.
If you have a pinax application, take a look in the requirements directory.
You'll find two files (base.txt and project.txt) that tell exactly what
application to get and what vers
*I bet you installed pinax on your linux box but not on your osx one (or not
in the same virtual env).*
*hmmm, I just copied the code from Linux to OSX, is it what you mean? I
should have "install" Pinax, that's it?*
On Tue, Aug 10, 2010 at 12:05 PM, Xavier Ordoquy wrote:
>
> Actually, it doesn't
Actually, it doesn't work on Linux either with the same settings.
Please update django-timezones to 0.2.dev2 which is what pinax uses (pip
install --extra-index-url=http://dist.pinaxproject.com/dev/
django-timezones==0.2.dev1). The latest stable doesn't seem to work with django
1.2.
I bet you i
I'm not blaming OSX.
I just said that it was working on Linux, and now it's not working on Mac.
and even if my code is wrong that shouldn't be that dificulty to find the
error, doesn't agree? A more clear error message would help.
The problem isn't the error, but we are about a month arguing about
Le 10 août 2010 à 15:10, Daniel França a écrit :
> It's very useful Andy, sympathy is welcome =)
> I was programming under linux, and I guessed that would be really straight
> forward port my project to OSX, I was wrong :(
You know you are unfair. Unless you have strong evidence, you shouldn't
It's very useful Andy, sympathy is welcome =)
I was programming under linux, and I guessed that would be really straight
forward port my project to OSX, I was wrong :(
> 2010/8/10 AndyB
>
> I haven't got anything useful to add other than some sympathy. I
>> vented my incoherent rage on Twitter a
I'll try to update my code.
On Tue, Aug 10, 2010 at 10:06 AM, Xavier Ordoquy wrote:
> Actually I have pinax (trunk) running with the social template and django
> 1.2 without issue using sqlite on OSX.
> I can change my profile timezone in this application without any issue,
> everything seems to
Actually I have pinax (trunk) running with the social template and django 1.2
without issue using sqlite on OSX.
I can change my profile timezone in this application without any issue,
everything seems to be working fine.
Somehow, the changes you made seem to have messed up something or you don'
the log files are for tests purposes only.
I'm inserting the site table myself.
is it a bug in pinax profiles? accounts? I didn't get the point.
On Tue, Aug 10, 2010 at 9:10 AM, Xavier Ordoquy wrote:
> It is definitively an issue in your code.
>
> syncdb won't run without complaining about the
It is definitively an issue in your code.
syncdb won't run without complaining about the timezone field in your account
model.
Once commented, syncdb continues but at some point will fail because it expects
a site to be configured but at this point, the site table is not garanteed to
be there..
ahh... and my code is in github
if someone wanna test it: http://github.com/danielfranca/Tint
2010/8/10 Daniel França
> My code is based on Pinax: http://pinaxproject.com/
> and the Profile comes from there.
>
>
> On Tue, Aug 10, 2010 at 5:33 AM, tsmets wrote:
>
>> My feeling is that you are no
My code is based on Pinax: http://pinaxproject.com/
and the Profile comes from there.
On Tue, Aug 10, 2010 at 5:33 AM, tsmets wrote:
> My feeling is that you are now hitting a bug from your app & not a
> django / python / mac / ... issue.
> A stupid gess from me ...
> You use a Custom Profile fo
My feeling is that you are now hitting a bug from your app & not a
django / python / mac / ... issue.
A stupid gess from me ...
You use a Custom Profile for the User and it is an upgrade from Django
1.1 and ... you need to adapt the minor details about it .
If you code is in a SVN server I can do a
Hi, thanks, I didn't know this werkzeug debuger.
Now I can see exactly where it raises the error and can print the variables
values, here's the output with some values:
File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py",
line *20
Please, install django_extentions, werkzeug debuger and try to see what exactly
where the issue is with the runserver_plus command (in browser debugger so
you'll get the variables that are missing here.
Most probably, your timezone field causes the issue.
Regards,
Xavier.
Le 9 août 2010 à 22:40
Thanx for all the help,
I tried to run on Sqlite3, and I don't if it's bad or good news, but there's
error even in Sqlite3
just when I tried to create the db (syncdb) I get just after I input my
users data or when I try to create a user in shell:
Traceback (most recent call last):
File "manage.p
I use PostgreSQL on my Mac as well as MySQL, and I've had many fewer
problems with PostgreSQL than I've had with MySQL.
My personal opinion: Ignore all the ports/fink stuff, and get a good
native PostgreSQL install:
http://postgresqlformac.com
The 8.4.3 installer has some known problems (easy to
Daniel,
Did you manage to have the application running on sqlite3 ... ?
I develop on Mac & have few issues... so may be you could first ensure
everything is working without postgresql connector ... ?
\T,
On Aug 9, 4:24 am, Daniel França wrote:
> tried, nothing :(
> I'm getting crazy with Mac OS
I haven't read all the comments here but if you've just started
working on osx you should definitely check out http://github.com/mxcl/homebrew
- it's a package manager which works like a charm most of the time.
Installation is extremely simple (there is even one-liner available).
If your problem i
I doubt it's a mac issue.
I already ran in a couple of very painful issues with postgresql on Linux while
having no issue with mysql on mac.
My feeling is that postgresql require far more attention than mysql and is more
sensitive to small changes.
Regards,
Xavier.
Le 9 août 2010 à 05:32, Danie
yeah, psycopg2
On Mon, Aug 9, 2010 at 1:27 AM, Sam Lai wrote:
> 2010/8/9 Daniel França :
> > I tried to reinstall everything... installing python+postgres from ports
> > and I get the Symbol not found: _PQbackendPID error again from psycopg.
> > I guess the best solution is run Ubuntu on a virtu
2010/8/9 Daniel França :
> I tried to reinstall everything... installing python+postgres from ports
> and I get the Symbol not found: _PQbackendPID error again from psycopg.
> I guess the best solution is run Ubuntu on a virtual machine or my project
> will be stuck forever.
> python+psycopg on mac
I tried to reinstall everything... installing python+postgres from ports
and I get the Symbol not found: _PQbackendPID error again from psycopg.
I guess the best solution is run Ubuntu on a virtual machine or my project
will be stuck forever.
python+psycopg on mac just sux.
2010/8/8 Daniel França
tried, nothing :(
I'm getting crazy with Mac OS, I think I'll go back to Linux :S
On Sun, Aug 8, 2010 at 4:34 AM, Xavier Ordoquy wrote:
> It won't work by commenting the timezone field since it has been created
> with a non null constraint on your db.
> Have you tried to get_or_create the accoun
It won't work by commenting the timezone field since it has been created with a
non null constraint on your db.
Have you tried to get_or_create the account with timezone and language set to
some value ?
Regards,
Xavier.
Le 8 août 2010 à 04:09, Daniel França a écrit :
> More information.
> here
More information.
here:
def create_account(sender, instance=None, **kwargs):
if instance is None:
return
account, created = Account.objects.get_or_create(user=instance)
post_save.connect(create_account, sender=User)
If I comment the *post_save.connect*, there's no exception =) but
Xavier, I think we are almost there :P
because there's a timezone field in my account model:
class Account(models.Model):
user = models.ForeignKey(User, unique=True, verbose_name=_('user'))
timezone = TimeZoneField(_('timezone'))
language = models.CharField(_('language'), max_length=
And what's your Account model ?
I noticed it is in its get_or_create that you get the error.
Regards,
Xavier.
Le 7 août 2010 à 18:52, Daniel França a écrit :
> Same error =/
> but now,I don't know why.. it's saving at the db. The error still happens,
> but the data is in the database
>
> On Sa
Same error =/
but now,I don't know why.. it's saving at the db. The error still happens,
but the data is in the database
On Sat, Aug 7, 2010 at 12:54 PM, Xavier Ordoquy wrote:
> Sorry, I just woke up form a sleep :)
> I notice you get-or-create a user.
> However, did you try to call get or create
Sorry, I just woke up form a sleep :)
I notice you get-or-create a user.
However, did you try to call get or create with specifying the arguments ?
first_name = "...", and so on ?
Does it still give an error ?
Regards,
Xavier.
Le 7 août 2010 à 17:46, Xavier Ordoquy a écrit :
> I just googled yo
I just googled your error and found:
http://www.nerdydork.com/django-programmingerror-cant-adapt.html
According to the first comment, you might do something wrong with the arguments
types.
Unless you give a table description (\d from psql shell) and the model I'm not
sure I can help you further.
I just created my db using django manage syncdb, I think it should create
right.
or how can I see the encode of each tables?
I'm using postgresql 8.4
maybe I'll need reinstall everything =S
On Sat, Aug 7, 2010 at 6:49 AM, Xavier Ordoquy wrote:
>
> Le 7 août 2010 à 06:44, Daniel França a écrit :
Le 7 août 2010 à 06:44, Daniel França a écrit :
> My database is UTF-8, it's fine, doesn't?.
> I'm afraid to reinstall everything from ports and start to get a lot 64-32
> bits incompatible issues like happened before =/
I think that should be fine with a utf-8 DB.
Are you sure your tables are
My database is UTF-8, it's fine, doesn't?.
I'm afraid to reinstall everything from ports and start to get a lot 64-32
bits incompatible issues like happened before =/
2010/8/6 Daniel França
> ops, sorry. python 2.7 django 1.2.1 =}
> thanx, I'll look at this
>
>
> On Fri, Aug 6, 2010 at 1:02 PM,
ops, sorry. python 2.7 django 1.2.1 =}
thanx, I'll look at this
On Fri, Aug 6, 2010 at 1:02 PM, wrote:
> Hi daniel,
>
> I doubt your python version is 1.2.1, maybe it's rather Django version :)
> However, the issue django stated looks pretty clear to me. You created a
> database with a wrong enc
Hi daniel,
I doubt your python version is 1.2.1, maybe it's rather Django version :)
However, the issue django stated looks pretty clear to me. You created a
database with a wrong encoding type.
You should have a look at:
http://docs.djangoproject.com/en/1.2/ref/unicode/
Regards,
Xavier.
On Fri,
Hi, I'm still get error trying to run my project on Mac =(
Now the standalone server is running fine, but when I try to create a new
user I get the error: "Can't adapt type 'US/Eastern", I tried to change my
TIME_ZONE in setting, but no success.
I can simulate this error in console, and here's the
thanks a lot, now it's working.. at least this part.
=)
On Sun, Jul 18, 2010 at 11:10 PM, Shawn Milochik wrote:
> This is a known (and common) problem. Here's an easy fix that I've used
> many times.
>
> http://shawnmilo.blogspot.com/2009/11/psycopg2-on-snow-leopard.html
>
> Incidentally, you ca
This is a known (and common) problem. Here's an easy fix that I've used many
times.
http://shawnmilo.blogspot.com/2009/11/psycopg2-on-snow-leopard.html
Incidentally, you can replace "make install" with "make altinstall" to add
Python 2.7 to your system without replacing the default Python.
Sha
47 matches
Mail list logo
