Akagra

At home I have a desktop computer that I use mostly for gaming. I have a laptop that I use for my home office work and development. I often use a Windows Remote Desktop Connection to use my laptop (that is sitting in my office) while I am in the living room where my desktop is. Today I needed to create some ISO images from CDs and burn some ISOs to disc. I didn’t want to run back and forth between my living room and my office.

Then I remembered that I had Alcohol 52% on my desktop and Alcohol 120% on my laptops.

I used Alcohol 52% to share the DVD-RW on my desktop using Alcohol iSCSI Server and my laptop is running Vista, so I used Vista’s built-in iSCSI client and mounted the drive.

Now I could use the DVD-RW drive that was physically on my desktop with Alcohol 120% running on my laptop over a Remote Desktop Connection.

Download http://peak.telecommunity.com/dist/ez_setup.py and execute it.

wget http://peak.telecommunity.com/dist/ez_setup.py
chmod 777 ez_setup.py
python ez_setup.py

I can never seem to remember the steps despite it being so simple. I just don’t do it enough to remember.

mkdir .ssh
chmod 700 .ssh
cd .ssh
vi authorized_keys
// paste public key
chmod 600 authorized_keys

I am running on Windows and using JP Software’s Take Command version 10. I also like to use IPython.

When I invoke IPython from a TCC shell I have problems with aliases that shell out to TCC from IPython. For example, a simple ls command.

I discovered that the DOS/TCC environmental variable COMSPEC is set to a value that includes a space (C:\Program Files\JPSoft\TCMD10\TCC.EXE). If I set it to the 8.3 value (C:\PROGRA~1\JPSoft\TCMD10\tcc.exe) before invoking IPython, all is well.
Read the rest of this entry »

I’m on Windows and I have created a virtualenv sandbox. I activate the sandbox and now I want to start up an IPython shell using the sandboxed environment. The following will do just that.

python -c "import IPython.Shell; IPython.Shell.IPShell().mainloop(sys_exit=1)"

thx to ThomasWaldmann on #python
Read the rest of this entry »

Today I wanted to install the Python Cryptography Toolkit into a sandbox I had created using virtualenv. The issue was that the PCT was available as a Windows binary at The Voidspace Python Modules but I didn’t know how to install it to a sandbox because the EXE installer looks to the registry for the location of the system installation of Python.

After a little searching and experimenting I realized that all you need to do is to change the location the registry is point to from the system installation of Python to the sandboxed version.

So in my case I backed up the current registry key.

REGEDIT4
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.6\InstallPath]
@="C:\\Python26\\"

And then created a copy of the file and modified it to point to the sandboxed Python install.

REGEDIT4
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.6\InstallPath]
@="D:\\workspace\\mysandbox\\"

At this point you simply run the EXE installer and it will be installed to the sandbox. After it is installed, restore the original registry key.

update:

I am running 64-bit Windows 7 on one of my computers and see that the corresponding registry entry is at:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Python\PythonCore\2.6\InstallPath