Python developer salary September 2017

United States Python developers labor market analysis according to the results of September, 2017
11 September 2017   458

We publish the analysis of the labour market of developers in the United States monthly. For Python developers there were 1404 vacancies. The vacancy rates were distributed as follows. 

Salary Estimate Python September 2017Python developer salary estimate 

Most of the developers are required in New York, NY; the least in Santa Clara, CA.

Number of vacancies in different cities Python September 2017Number of Python developer vacancies in different cities 

Among the companies that hire Ruby on Rails developers the leaders are: 

  • Smith & Keller
  • Jobspring Partners
  • Workbridge Associates

Number of vacancies in different companies Python September 2017 Number of Python developer vacancies in different companies 

According to the experience required, the vacancies are distributed as follows. 

Number of vacancies by experience level Python September 2017 Python developer vacancies by the experience level

The average salary and salary according to the level of experience were distributed as follows.

Average salary Python September 2017 Python developer average salary

The analysis was carried out by the Hype.codes portal method using the indeed.com data.

What is YAPF?

A formatter for Python files, developed by Google team
30 October 2017   443

What is YAPF?

Most of the current formatters for Python --- e.g., autopep8, and pep8ify --- are made to remove lint errors from code. This has some obvious limitations. For instance, code that conforms to the PEP 8 guidelines may not be reformatted. But it doesn't mean that the code looks good.

YAPF takes a different approach. It's based off of 'clang-format', developed by Daniel Jasper. In essence, the algorithm takes the code and reformats it to the best formatting that conforms to the style guide, even if the original code didn't violate the style guide. The idea is also similar to the 'gofmt' tool for the Go programming language: end all holy wars about formatting - if the whole codebase of a project is simply piped through YAPF whenever modifications are made, the style remains consistent throughout the project and there's no point arguing about style in every code review.

The ultimate goal is that the code YAPF produces is as good as the code that a programmer would write if they were following the style guide. It takes away some of the drudgery of maintaining your code.

Code examples

YAPF takes this code:

x = {  'a':37,'b':42,

'c':927}

y = 'hello ''world'
z = 'hello '+'world'
a = 'hello {}'.format('world')
class foo  (     object  ):
  def f    (self   ):
    return       37*-+2
  def g(self, x,y=42):
      return y
def f  (   a ) :
  return      37+-+a[42-x :  y**3]

and reformat it into:

x = {'a': 37, 'b': 42, 'c': 927}

y = 'hello ' 'world'
z = 'hello ' + 'world'
a = 'hello {}'.format('world')


class foo(object):
    def f(self):
        return 37 * -+2

    def g(self, x, y=42):
        return y


def f(a):
    return 37 + -+a[42 - x:y**3]

See GitHub for more information.