Stabby McDamage posted:

I just noticed that I can do "a not in b" just as well as "not a in b". That's cool, but weird to me. "not" can modify "in", but not other comparators...I can't say "a not > b". Is there a name for this behavior?

tripwire posted:

not doesn't modify an operator, it modifies a boolean.

>>> not True
False

tef posted:

Essentially, there is an "in" operator, and a "not in" operator. There are also "is" and "is not" operators.

(although a similar thing is the notion of 'adverb methods' in ruby http://weblog.raganwald.com/2008/07/that-not-is-not-not-i-meant.html )

haywire posted:

Has anyone checked out gevent or denied yet? I've been playing around with Denied, it seems very nice - it isn't in that extensive server benchmark yet, but it's been getting people talking.

Also need to start playing around with thrift and cassandra and couchdb.

For those wanting to start using Gevent, I wrote a super simple "Hello World" app, that runs in separate greenlets:

code:

import gevent

def hello( name ):
        return "Hello, %s!" % name

if __name__ == '__main__':
        names = [ "James", "Ruth" ]
        jobs = [ gevent.spawn( hello, name ) for name in names ]
        gevent.joinall( jobs )
        for job in jobs:
                print job.value

Khorne posted:

What is the best python equivalent of:

someVar = !someVar

Google is just turning up a lot of things that aren't helping. They either seem excessively long or not applicable to the question.

UberJumper posted:

Does anyone know what can be causing duplicate logging messages to be outputted?

code:

[DEBUG   ] 20100402 21:01:07 | auxpy.util.gen_generator | Interface Found
DEBUG:auxpy.util.gen_generator:Interface Found

In the auxpy.__init__.py i declare the root logger as

code:

_logger = logging.getLogger(__name__)
_logger.addHandler(NullHandler())

then i have a simple test file that changes this value into a stream logger for debugging.

Ive checked and all the loggers use, __name__ to get the logger.

Is there anyway to check this?

BeefofAges posted:

Try checking how many handlers that logger has. Each handler will do its own log output. You can try printing _logger.handlers

deimos posted:

Try using pip, it's less retarded than easy_install.

Ghetto Wizard posted:

I've been trying to install lxml properly for 3 days now and I really can just not make it work properly. I keep getting this error:

code:

>>> from lxml import etree
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: /usr/local/lib/python2.6/site-packages/lxml-2.2.5-py2.6-linux-i686.egg/lxml/etree.so: symbol xmlSchematronSetValidStructuredErrors,
version LIBXML2_2.6.32 not defined in file libxml2.so.2 with link time reference

libxml2 and libxslt are both installed and so are the dev packages, aswell as the python dev package. I used easy_install to install lxml. I've downgraded to earlier versions of lxml and I still get the same error. I don't know what to do really.

edit: oh right, I use Debian 4.0

tripwire posted:

Are you installing lxml from the debian package repo or are you building from source?

Ghetto Wizard posted:

Pip finds packages automatically and builds them using that, but I'm not manually building it from source, though it is apparently possible.

Here's the pip install process of lxml:

code:

Downloading/unpacking lxml
  Downloading lxml-2.2.6.tar.gz (2.9Mb): 2.9Mb downloaded
  Running setup.py egg_info for package lxml
    Building lxml version 2.2.6.
    Building with Cython 0.12.1.
    Using build configuration of libxslt 1.1.26
    Building against libxml2/libxslt in the following directory: /usr/local/lib
    warning: no previously-included files found matching '*.py'
Installing collected packages: lxml
  Running setup.py install for lxml
    Building lxml version 2.2.6.
    Building with Cython 0.12.1.
    Using build configuration of libxslt 1.1.26
    Building against libxml2/libxslt in the following directory: /usr/local/lib
    building 'lxml.etree' extension
    gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/local/include
 -I/usr/local/include/libxml2 -I/usr/local/include/python2.6 -c src/lxml/lxml.etree.c
 -o build/temp.linux-i686-2.6/src/lxml/lxml.etree.o -w
    gcc -pthread -shared build/temp.linux-i686-2.6/src/lxml/lxml.etree.o -L/usr/local/lib -lxslt -lexslt 
-lxml2 -lz -lm -o build/lib.linux-i686-2.6/lxml/etree.so
    building 'lxml.objectify' extension
    gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/local/include
 -I/usr/local/include/libxml2 -I/usr/local/include/python2.6 -c src/lxml/lxml.objectify.c 
-o build/temp.linux-i686-2.6/src/lxml/lxml.objectify.o -w
    gcc -pthread -shared build/temp.linux-i686-2.6/src/lxml/lxml.objectify.o -L/usr/local/lib -lxslt -lexslt -lxml2 -lz -lm 
-o build/lib.linux-i686-2.6/lxml/objectify.so
Successfully installed lxml

_{It's really easy to break tables using code}

Ghetto Wizard posted:

I've been trying to install lxml properly for 3 days now and I really can just not make it work properly. I keep getting this error:

code:

>>> from lxml import etree
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: /usr/local/lib/python2.6/site-packages/lxml-2.2.5-py2.6-linux-i686.egg/lxml/etree.so: symbol xmlSchematronSetValidStructuredErrors,
version LIBXML2_2.6.32 not defined in file libxml2.so.2 with link time reference

libxml2 and libxslt are both installed and so are the dev packages, aswell as the python dev package. I used easy_install to install lxml. I've downgraded to earlier versions of lxml and I still get the same error. I don't know what to do really.

edit: oh right, I use Debian 4.0

Spime Wrangler posted:

Is there a standard way of avoiding this?

BeefofAges posted:

You could also just round the numbers off.

http://function.name/in/Python/round/

Avenging Dentist posted:

BeefofAges posted:

I suppose I should have clarified that as rounding them before printing. It's possible that he could end up with some number that wasn't nice and round, like .387453876583456 or whatever, and want to round it to just a few digits. Of course, since he's taking values in from a config file, that isn't all that likely. I don't know where I'm going with this. Whatever.

Avenging Dentist posted:

BeefofAges posted:

I suppose I should have clarified that as rounding them before printing. It's possible that he could end up with some number that wasn't nice and round, like .387453876583456 or whatever, and want to round it to just a few digits. Of course, since he's taking values in from a config file, that isn't all that likely. I don't know where I'm going with this. Whatever.

Avenging Dentist posted:

Aaaaaaaaaa gently caress you NumPy

code:

>>> A = numpy.arange(5)
>>> A[0:4] = A[3::-1]
>>> A
array([3, 2, 2, 3, 4])

Should be [3, 2, 1, 0, 4]

Modern Pragmatist posted:

I guess they don't make a copy of a before referencing.

Modern Pragmatist posted:

Is the best solution:

code:

A[0:4] = A.copy()[3::-1]

Avenging Dentist posted:

I know why it's that way but it's beyond retarded that they don't check for it in the assignment, especially since it's trivially easy (A[3::-1].base is A).


Actually it'd be better to put the copy at the end so you aren't copying the whole array.

Mostly I was just complaining though.

king_kilr posted:

So file a bug, or ask on their mailing list. It may be that it's intentional.