On 10/09/2013 07:49 PM, Glyph wrote:
On Oct 9, 2013, at 12:16 PM, Steve Waterbury <water...@pangalactic.us <mailto:water...@pangalactic.us>> wrote:... in particular, why it doesn't make sense to 'pip install' pyjs.Personally I'd love to be able to 'pip install' it simply so that I can do 'pip install pyjs' and then get pyjampiler and pyjsbuild on my $PATH automatically, since pip provides nice tools and automation for that. Plus that would make it easier for build systems that already support setuptools (debian, fedora, et. al.) to build ready-made PyJS packages.
I think it would be easy enough to create a pip install that does what you suggest. I suppose for some uses having that stuff on your path might be good; however, some configuration is always needed to use it for development, so just having that stuff in your $PATH is not a big win, IMO. For example, for each app that you are creating you will need to decide what parameters and paths to use when you run pyjsbuild, which you will do every time you make a change to your app code. The suggested way to do that is a build.sh script -- I've attached one of mine so you can see an example. Since build.sh is simply a shell wrapper for pyjsbuild, there's really no need to have pyjsbuild on your path. NOTE: as you can infer from the path names in my build.sh, I am using pyjs in a directory that is located inside a virtualenv, but the virtualenv is for the backend [Django] of the app, not for pyjs -- i.e., the pyjs libraries are not "installed" in the virtualenv. I keep my own library of widgets derived from pyjs widgets in a separate repository, but I manage my app-specific pyjs code in the same repository with the Django backend code for the app, in a directory called "customjammies", which is purposely not a python package so it's invisible to the Django app -- pyjsbuild includes it in the "build" because of the '-I' flag.
This would also make it a lot easier for PyJS to depend on other Python projects for its own use, so that they could be automatically installed. If PyJS is to be split up into multiple pieces, it should be able to use *itself* as a Python library :-).
It already does that ... or else I don't understand what you're saying.
I'd have no expectation that after 'pip install' it would be usable as a regular platform Python library though.
No, that would make absolutely no sense at all. Steve ----- You received this message because you are subscribed to the Google Groups "Pyjs.org Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyjs-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
build-boson.sh
Description: application/shellscript
