@property causes errors due to incorrect generated code

Reproduce the MWE and inspect the generated props.js output alongside the get implementation shown in the issue. Trace the generated Foo property definitions and property access, then verify that both properties reference the correct implementation functions and return values rather than attempting to call them.

MWE:

class Foo:
	@property
	def bar(self):
		return 'Hello World'
	
	@property
	def name(self):
		return 'John Smith'

foo = Foo()

print(foo.bar) # Should print "Hello World"
print(foo.name) # Should print "John Smith"

The relevant Transcrypt output is:

var Foo = __class__ ('Foo', 'props', [object], {
	__impl__bar: function (self) {
		return 'Hello World';
	},
	get bar () {return __get__ (this, this.__impl__bar);},
	__impl__name: function (self) {
		return 'John Smith';
	},
	get py_name () {return __get__ (this, this.__impl__name);}
})
Object.defineProperty (Foo, '__impl__bar', property.call (Foo, Foo.Foo.__impl__bar));;
Object.defineProperty (Foo, '__impl__name', property.call (Foo, Foo.Foo.__implpy_name));;;

Note that __impl__bar is defined as Foo.__impl__bar, but is referenced in the defineProperty call as Foo.Foo.__impl__bar. This causes an error, as Foo.Foo is undefined:

.../props.js:2450
                Object.defineProperty (Foo, '__impl__bar', property.call (Foo, Foo.Foo.__impl__bar));;
                                                                                       ^

TypeError: Cannot read property '__impl__bar' of undefined

A simple workaround is to patch the output: perl -0777 -pi -e 's/property.call \((.*?), \g1.\g1.__impl__(.*?)\)/property.call ($1, $1.__impl__$2)/g' path/to/file.js

Note that for Foo.name, there is a slightly different problem as well, in that the function is defined as __impl__name, but is referenced as __implpy_name, causing a further error.

Again, a simple workaround suffices for now: perl -0777 -pi -e 's/property.call \((.*?), \g1.\g1.__implpy_(.*?)\)/property.call ($1, $1.__impl__$2)/g' path/to/file.js

Even after applying these patches however, @property is still not functional because e.g. foo.bar ends up being wrapped as a function that attempts to "call" foo.bar. This, of course, fails, because foo.bar is not a function.

The issue appears to be in the implementation __get__:

var __get__ = function (self, func, quotedFuncName) {
	if (self) {
		if (self.hasOwnProperty ('__class__') || typeof self == 'string' || self instanceof String) {           // Object before the dot
			if (quotedFuncName) {                                   // Memoize call since fcall is on, by installing bound function in instance
				// ...
				// The property is defined as a function instead of a value

Inserting a statement if(typeof(func) != "function"){return func;} at the very beginning of this function seems to fix the issue.