Currency converter in Python 2.7
Never assume that your user doesn't make mistakes.  I ran your program with no arguments ... error message, fine.  I ran it with a single argument of 4 ... error message, fine.  I ran it with two arguments, 4 and 5 ...:

Traceback (most recent call last):
  File "test.py", line 17, in &lt;module&gt;
    rate = checker(args.curency_for_convert, args.curency_converted_to)
  File "test.py", line 9, in checker
    rate = content["rates"][symbol.upper()]
KeyError: 'rates'


For debugging purposes, I put print content above that line and ran again:

{'error': 'Invalid base'}


If I run the program with a valid base, but an invalid symbol:

Traceback (most recent call last):
  File "test.py", line 16, in &lt;module&gt;
    rate = checker(args.curency_for_convert, args.curency_converted_to)
  File "test.py", line 8, in checker
    rate = content["rates"][symbol.upper()]
KeyError: '8'


You should catch these errors and display something that is a little more user-friendly.



I would recommend that you read PEP 8, the Python style guide.  There are a couple things you aren't following:


  Imports should usually be on separate lines, e.g.:
  
  Yes:

import os
import sys

  
  No:

import sys, os

  
  It's okay to say this though:

from subprocess import Popen, PIPE






  Don't use spaces around the = sign when used to indicate a keyword argument or a default parameter value. 




Your whitespace is a little strange.  I would have at least one blank line above and below the function definition.  I would also put one after the if block and maybe even before it too.  You have " =", " = ", and "=" used in just three lines.  PEP 8 says that A Foolish Consistency is the Hobgoblin of Little Minds, but that doesn't mean never be consistent.  It is only the foolish consitency which is a hobgoblin.  In this case, you have nothing to lose.

Your naming is a little strange.  n even shows up in the help messages.  One-letter variable names are generally not recommended because they give very little idea of what the variable is for.  curency_for_convert and curency_converted_to, besides mis-spelling "currency", are ungrammatical.  You could say "for conversion" or "to convert", but "for convert"?  I would suggest "convert_from" and "convert_to".


if len(sys.argv) &gt; 3:
    parser.add_argument("n", type =int, help = "Amount of curency_for_convert", default=1)



Instead of manually parsing an argument, make it optional with nargs='?'


print rate if len(sys.argv) &lt;= 3 else rate*args.n



Since our argument will always be present (either with the default of 1 or with a user-supplied number), we can now do print rate * args.n.

Full Program

#!/usr/bin/env python
import argparse
import ast
import requests
import sys

def checker(base, symbol):
    url = "http://api.fixer.io/latest?base=%s" % base.upper()
    r = requests.get(url)
    content = ast.literal_eval(r.content)
    rate = content["rates"][symbol.upper()]
    return rate

parser = argparse.ArgumentParser(description=
    "Currency converter. For instance: to convert 100 USD to RUB, it would be "
    "100 USD RUB. If you need only the rate: USD RUB"
)

parser.add_argument("amount", type=int, help="Amount of currency to convert", default=1, nargs='?')
parser.add_argument('convert_from', type=str, help="Currency to convert")
parser.add_argument('convert_to', type=str, help = "Currency of converted")

args = parser.parse_args()

try:
    rate = checker(args.convert_from, args.convert_to)
except KeyError:
    print "Invalid argument(s)"
else:
    print rate*args.amount