I am having trouble getting the PyBWidgets plugged in correctly in a Windows XP environment. It appears to be path-related, since the BWidget package can't be found. The installation 'Read Me' indicates that I should 'package require'--what does this mean and how would I do this?
> Hello All:
> I am having trouble getting the PyBWidgets plugged in correctly in a Windows XP environment. It appears to be path-related, since the BWidget package can't be found. The installation 'Read Me' indicates that I should 'package require'--what does this mean and how would I do this?
"package require .." is something like the tcl equivalent to python's "import ...".
However, you shouldn't have to bother with this, it's something the python module should do for you.
Did you run the setup.py, and if yes, where did it install the BWidgets ?
On my linux box they're in /usr/share/pybwidget , I'm not sure about windows, but I think somewhere in
your Tcl folder should work.
> I guess I need to provide some additional commands,
> but I am not sure which commands I should provide.
python setup.py --help-commands
build build everything needed to install
build_py "build" pure Python modules (copy to build directory)
build_ext build C/C++ extensions (compile/link to build directory)
build_clib build C/C++ libraries used by Python extensions
build_scripts "build" scripts (copy and fixup #! line)
clean clean up output of 'build' command
install install everything from build directory
install_lib install all Python modules (extensions and pure Python)
install_headers install C/C++ header files
install_scripts install scripts (Python or otherwise)
install_data install data files
sdist create a source distribution (tarball, zip file, etc.)
register register the distribution with the Python package index
bdist create a built (binary) distribution
bdist_dumb create a "dumb" built distribution
bdist_rpm create an RPM distribution
bdist_wininst create an executable installer for MS Windows
given your subject line, "install" might be what you want.
reading the generic installation guide can also be a good idea:
I see what was happening here. I was running 'setup.py --help-commands' and my text editor was just opening up the file. I wasn't assuming the obvious, which was that I should have been entering 'python setup.py --help-commands'. I have gone down the 'python setup.py install' route and everything is working great.