Support alternative import / export syntax about metapensiero.pj HOT 10 CLOSED

Also I think related to this is support for export default syntax.
The question is how to implement it? If __all__ is not a list, perhaps?

from metapensiero.pj.

so the function/class is accessible at vue.Vue?

the standard Python's:

from vue import Vue 

should work in that case or

import vue as Vue

if it's a default import:

$ pj -s -
from vue import Vue
import vue as Vue 

import {Vue} from 'vue';
import * as Vue from 'vue';

About the default exports, I simply don't think it's much of a feature.. anywayI've thought about using all too, but doesn't seem right...

from metapensiero.pj.

I had tried that and I couldn't get it to work but now I learned it was because of an issue with Webpack and module loading webpack/webpack#4039 - apparently you can't mix import and module.exports so it's a small but important feature.

from metapensiero.pj.

I guess import {Vue} from 'vue' is different from import Vue from 'vue'.
I was able to get the behaviour I need with from vue import default as Vue:

<script lang="py?compiler=pj">
from vue import default as Vue
from vue__codemirror__lite import default as VueCodeMirror

Vue.use(VueCodeMirror)

class Component:
    def __init__(self):
        self['data'] = lambda: { 'code': '2' }
        self['computed'] = { 'data': lambda: 2 }

__all__ = Component()
</script>

from metapensiero.pj.

That is after applying patch for default export.

from metapensiero.pj.

I was wrong, this should be the "non obvious" default import using named imports:

import {default as bar} from 'foo';

from metapensiero.pj.

@icarito Please see the referenced commit and see if it now works for you!

from metapensiero.pj.

I still have to update the docs

from metapensiero.pj.

Thanks for your updates! Also I suggest to implement anonymous default export as in https://gitlab.com/metapensiero/metapensiero.pj/merge_requests/35

from metapensiero.pj.

Hi @icarito, I'm closing this. It seems superseded by the changes in the repo. Open a new one for any remaining issues. Also note that i've made a new release, so you don't have to refer directly to a snapshot of the repo in your requirements.txt

from metapensiero.pj.