HCoder.org comments

"Frustrated by Python module management" by Esteban

Mon, 30 Jun 2008 13:28:48 +0100

Hey, thanks for the comments!

Michael: No, that machine is only used for automated test runs. Several different projects though. BTW, I didn’t install SQLAlchemy in development mode, just with a regular easy_install… but for some reason Python sometimes “forgets” that it’s actually there (it gets lost from easy_install.pth somehow, but I have no idea why). When you say “installing normally”, do you mean in the system, like in /usr/lib/python/site-packages ? I’d rather not do that if possible, but installing in some “private directory” and using from there would be possible of course.

Sverre: PYTHONPATH didn’t work for me, maybe I did something wrong? Am I supposed to install things first so it works, or should I be able to just point PYTHONPATH to the directory with a fresh VCS checkout?

And thanks for the virtualenv thing, I’ll have a look!

Oh, and sorry for the comments not appearing, I was receiving tons of spam so I decided to make the comments invisible until I approved them… I didn’t really expect showing up on reddit :-P

"Frustrated by Python module management" by Sverre Johansen

Mon, 30 Jun 2008 10:08:32 +0100

I can has documentation?

http://docs.python.org/dev/install/index.html#inst-search-path

"Frustrated by Python module management" by Sverre Johansen

Mon, 30 Jun 2008 10:01:21 +0100

What is it that is so hard to understand?

If you want to you can just set the PYTHONPATH manually, the setup.py develop is just a convenience for you. I fail to see how Python package lookup is different from any other platform you are familiar with. It might work much better on Plan9 or some shit like that, but … ... :-)

Using setuptool and setup.py develop it will install the package in your python packages folder, which on Debian is by default the system folder, which will be shared by all users.

Probably the easiest for you (And Jonathan told me he already recommended it to you) is to use virtualenv – http://pypi.python.org/pypi/virtualenv

Also this discussion probably belong in an internal mailing list of some sort :)

"Frustrated by Python module management" by Eric

Mon, 30 Jun 2008 08:02:50 +0100

You should check out virtualenv. It lets you create a somewhat sandboxed python install for different projects. The biggest benefit is being able to have a separate place to install modules. I’ve done this in order to differentiate between projects I am working on and applications that run on my machine. This way I can verify what the dependencies really are as well as have an easy way to install two libraries at the same time. Good luck!

"Frustrated by Python module management" by alonlevy1@gmail.com

Sun, 29 Jun 2008 13:15:26 +0100

why not use python setup.py install? It installs to the /usr/lib/python/site-packages directory on python.

also, you should make sure you are using the same version of python for both the “python setup.py install” and running. If you have two versions, i.e. python2.4 and python2.5, you could by accident end up with a module installed for 2.4, but actually needed in 2.5.

as a debugging measure, start a python shell and do: import sys print sys.path

you’ll get the list of directories searched for your install. make sure to use the right python version like mentioned before.

PYTHONPATH should also work well (has for me). Have you exported it? i.e. export PYTHONPATH=/home/me/pythonlibs python myprog.py

or just prepend to the command line: PYTHONPATH=/home/me/pythonlibs python myprog.py

"Frustrated by Python module management" by Michael Foord

Sat, 28 Jun 2008 14:02:15 +0100

Certainly using setup.py develop on a machine on which you are running automated tests sounds like a bad idea.

Are you using the same machine for running automated tests (on several branches) and development (on several branches)?

Unless you are actually developing SQLAlchemy then you shouldn’t install it in development mode.

I would have all modules you depend on installed ‘normally’. Modules you are developing I personally wouldn’t have them installed at all, but keep them within my project structure and rely on the development / test environment to make sure they can be imported.

Polluting your test environment from your development environment should be avoided…

"Wiki- and Uncyclopedia on Scientology" by erGuiri

Thu, 15 May 2008 21:14:47 +0100

Shame on you! You forgot to mention we (people from Las Palmas) are greatly connected to scientology… you’d think all those tourists come for the weather… but they come (the ones that come on cruisers most of all) for historical reasons as one of the two planetary Implant Stations was located in our city!

Even though this is mentioned in uncyclopedia and may seem a joke, it is totally true “cos wikipedia sez so” too.

This one’s funny too:

http://uncyclopedia.org/wiki/Canary_Islands

"I don't "git" it" by emanchado

Wed, 14 May 2008 18:29:39 +0100

Yeah, I know. I meant more in the context of DVCS. Most Git users seem to defend it over, say, Mercurial, which looks pretty powerful, easily extensible with Python, and it’s distributed too anyway. And I, that I don’t get Git yet, wonder if it will really be better than Mercurial for “not huge” projects, because I feel that even if Git is more powerful, that power won’t really make a difference in those projects, and Mercurial’s better interface will have a much bigger impact, everyday for almost every member of the team.

About the opera:talks, yeah, that’s a good idea. I’ll talk to someone and try to get that rolling…

"I don't "git" it" by Vetle

Wed, 14 May 2008 08:12:20 +0100

If you’re used to SVN or CVS, then anything is better. Btw, can you please tell them to upload opera:talks to YouTube? =)

"I don't "git" it" by Sverre Johansen

Wed, 14 May 2008 00:20:56 +0100

The only thing that makes sense in git is the lower level stuff – how everything is screwed and bolted together. It is based on a really simple, and to me clever, architecture. But the UI and the documentation really does kind of suck.

But the big advantage lays in the community. Because it is made by this motley crew of rockstar programmers all the kids dig it, and blogs about all the stuff that the retarded documentation is unable to explain you. All your answers are one google away.