Skip to content

setup.py #2

Open
certik opened this Issue Feb 24, 2011 · 1 comment

2 participants

@certik
Qsnake member
certik commented Feb 24, 2011

Making py2js setup.py installable would make it easier to try out deploy etc.

Comments
certik May 14, 2010 | link | edit | delete
That's a good idea. Where should we put the py-builtins.js and later on possibly other scripts?

panosl May 14, 2010 | link | edit | delete
distutils has two options for this.
1. http://docs.python.org/distutils/setupscript.html#installing-package-data

If the *.js files are considered data it's under

package_data = {'py2js': ['data/*.js']}

http://docs.python.org/distutils/setupscript.html#installing-additional-files, where the layout might be like:
data_files = [('js': 'py-builtins.js')]

certik May 14, 2010 | link | edit | delete
Awesome, this should work. I am a bit busy today, do you think you can fix this in your branch? I'll merge it.

panosl May 14, 2010 | link | edit | delete
Which way do you wanna go though?

certik May 14, 2010 | link | edit | delete
Any way is fine with me. Choose one, it can always be changed later if it turns out that it doesn't work.

I guess that py2js.py should then somehow figure out the correct path to get the py-builtins.js, right?

@thenewguy

Is a setup.py script still planned?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.