[pid 16812] 11:15:24 select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)
[pid 16812] 11:15:25 gettimeofday({1250468125, 3388}, NULL) = 0
[pid 16812] 11:15:25 select(0, NULL, NULL, NULL, {0, 50000}) = ? ERESTARTNOHAND (To be restarted)
[pid 16812] 11:15:25 − SIGALRM (Alarm clock) @ 0 (0) −
[pid 16812] 11:15:25 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
[pid 16812] 11:15:25 − SIGSEGV (Segmentation fault) @ 0 (0) −
Process 16812 detached
[pid 16815] 11:15:25 +++ killed by SIGSEGV +++
Какой же все-таки веселый язык.
Вылечилось отключением сигналов через NOSIGNAL
/dev/md5 9.9G 9.4G 0 100% /var
/dev/md8 384G 62G 303G 17% /var/local/media
И ведь предупреждал же, что с таким разбиением места будет пиздец. Как же я ненавижу эту вашу планету.
Warning! This site is temporaly closed.
>> print u'\u4e03\u702c\u5149'七瀬光
>> print {'artist': u'\u4e03\u702c\u5149'}{'artist': u'\u4e03\u702c\u5149'}
>> {'artist': u'\u4e03\u702c\u5149'}.__repr__()"{'artist': u'\\u4e03\\u702c\\u5149'}"
>> {'artist': u'\u4e03\u702c\u5149'}.__str__()"{'artist': u'\\u4e03\\u702c\\u5149'}"
А мне нужно 'artist':'七瀬光' соответственно. Похоже придется свой сериализатор писать
query = 'select bet_id from bet where date_lifted is NULL and bet.content_id = %s and bet.user_id = %s' % (self.content_id, userid or 0)
found = meta.Session.execute(query).scalar()
return found
#return meta.Session.query(Bet).filter(Bet.content == self).filter(Bet.user_id == userid).filter(Bet.date_lifted == None).first()
dev.mysql.com
MySQL 5.0 supports two character sets for storing Unicode data:
— ucs2, the UCS-2 encoding of the Unicode character set using 16 bits per character
— utf8, a UTF-8 encoding of the Unicode character set using one to three bytes per character
These two character sets support the characters from the Basic Multilingual Plane (BMP) of Unicode Version 3.0. BMP characters have these characteristics:
— Their code values are between 0 and 65535 (or U+0000 .. U+FFFF)
— They are sufficient for almost all characters in major languages
Из-за чего в приложениях, использующих полноценный 4-байтный юникод, получаются весьма забавные ошибки.
MySQL 5.0 supports two character sets for storing Unicode data:
— ucs2, the UCS-2 encoding of the Unicode character set using 16 bits per character
— utf8, a UTF-8 encoding of the Unicode character set using one to three bytes per character
These two character sets support the characters from the Basic Multilingual Plane (BMP) of Unicode Version 3.0. BMP characters have these characteristics:
— Their code values are between 0 and 65535 (or U+0000 .. U+FFFF)
— They are sufficient for almost all characters in major languages
Из-за чего в приложениях, использующих полноценный 4-байтный юникод, получаются весьма забавные ошибки.
Python 2.6.2 (r262:71600, Jun 4 2009, 04:25:37)
>> def a(b={}):... b['c']=1
... return b
...
>> z = a(){'c': 1}
>> z
>> z['e']=2{'c': 1, 'e': 2}
>> z
>> d = a(){'c': 1, 'e': 2}
>> d
Постфактум обнаружил ворнинг в документации:
Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes.Хотя кто же её читает...