Skip to main content

Python script mysteriously refuses to run on Unix


Introduction

I was writing a new Python script (actually, a replacement for a bash script) at work today. I have a Windows laptop at work and in my projects and I often do development on Windows but the real objective is for the scripts and other work to run in a Unix system running under VirtualBox and Vagrant. To be exact, the system is: 
Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-143-generic x86_64)

Anyway, I was writing away and it worked ok up to a point on Windows but it needed resources on the Unix system so you might say it failed miserably but I was ready to try it on the virtual machine. When I tried, I got: 
(venv) vagrant@vagrant-host:/vagrant$ bruno/foobar.py --foo
: No such file or directory
(venv) vagrant@vagrant-host:/vagrant$

What the hell? That's a terrible error message. As an aside, I think some Python error messages can be awful and don't do a good job at fixing the problem. I think Python is a superb language but its error messages are not always the best.
Anyway, the error looked familiar but I couldn't remember what was wrong or how to fix it right off the bat. Some other facts:
  • The script uses #! /usr/bin/env python because the virtual machine has a newer version of Python in the $PATH which is supposed to override the system Python and I wanted to make use of it.
  • The script works fine if I do type python bruno/foobar.py --foo from the virtual machine command line but I don't want to have to do that.
  • I created the script on Windows using gvim
  • Remember, the script works fine from Windows!

Long story, short

After battling with this for several minutes, it finally dawned on me that I could be a poor victim of the Curse of the Carriage Return! When you create files on Windows, the file often has a carriage return character the precedes every newline character. Windows notepad is notorious for that - not only does it use carriage returns when you save a file but if you try to open a file that doesn't have carriage returns, it kind of acts like there are no newlines at all. Sometimes this can cause problems if you try to use the file in Unix or you might see funny symbols when you edit the file. There might be an option to not do that with gvim - I'll have to check that out.

I have a script called nocrs that can remove carriage returns on a file. Using that fixed up my script! Gosh, I just realized it's a bash script but that's ok with me.

Labels:

Comments

  1. John (aka Bruno)February 26, 2019 at 8:47 AM

    Recently I went back and rewrote my nocrs script as Python. I think I might have even made use of the logging and argparse modules. I've been loving using those lately.

    ReplyDelete

Post a Comment

Popular posts from this blog

Dynamic Python script loading

I have a bunch of toys and tools in a Git repository - I affectionately call this my toys repo . Most are just scripts that I use from a Unix (Cygwin or Git bash on Windoze) command line but there are some Python classes that I sometimes use in another script. Today at work, I was coming up with a new Python script that made use of a couple of my public classes. The script is good enough to share with my colleagues but I'm faced with the problem of my public classes: I imagine that most of my colleagues haven't even heard of my public classes and I don't expect them to download the entire repo just to get a couple of classes If I'm going to distribute the classes as separate files I introduce new problems: It could be confusing to have the files tag along. What is the user supposed to do with them? The answer is nothing - they should leave them alone and make sure they are in the same directory as the main script in case they decide to move th...
1 comment
Read more

Python ArgParse

Maybe it's my use of the getopt() function in C/C++ but in my Python scripts, I've always just made do with the native getopt package and it's served me well. Over time, people have encouraged me to look at using ArgParse but I've always been kind of resistant because it was a little mysterious to me. I finally sat down and figured out how to do basic things I do a lot in scripts using getopt and worked up a simple script using ArgParse to do the same thing. There are definitely some advantages to ArgParse ! Here's the gist with this sample: I've made a few updates to the gist as I discover new features of which I want to take advantage: Mutually-exclusive options Script description etc. I will admit that since I've created this gist, I've been using ArgParse for new scripts. I can't whip out a script using ArgParse from memory yet (which I can do when I use getopt !) but it's becoming easier. I haven't gone back and...
Post a Comment
Read more

Why I don't like Python 3

Why I don't like Python 3 Python 3 sucks.  I hate that they've made changes so that aren't backwards-compatible.  You can't run many Python 2 scripts using the Python 3 interpreter.  It's almost like they've gone out of their way to piss off developers. Here are some specific reasons why I hate Python 3: My biggest gripe: print is a function rather than a statement now.  I'm not saying it's not a good idea for print to be a function but why fuck with existing scripts?  Just keep the print statement as-is and create a new function with a distinct name. Data read from files comes back as bytes and you have to encode them.  More on this later but I think this is nonsense. You can't write a simple string to a file opened for binary.  Yes, I know about string.encode() but my point is I don't like having to use it. You can't turn off buffering when you open a text file for writing: open('foo', 'w', 0) throws  can...
1 comment
Read more