[Pythonmac-SIG] py2app, eggs and entry points
I have an application that I'd like to package using py2app, but I'm
getting a little stuck with things. I *think* my problem is that my
setup.py is fully setuptools-ized and my application script lives
inside my package. Here's the call I make to setup():
setup(name='cclookup',
version='2.0',
url='http://wiki.creativecommons.org/CcLookup',
author='Nathan R. Yergler',
author_email='[EMAIL PROTECTED]',
packages = ['cclookup', 'tagger', 'eyeD3'],
setup_requires = setup_requirements,
install_requires = ['setuptools',
'rdflib==2.3.3',
'ccrdf=0.6a4',
'cctagutils=0.5a1',
'rdfadict',
],
include_package_data = True,
zip_safe = False,
entry_points = {
'console_scripts':['cclookup = cclookup:main'],
},
app=['cclookup/app.py'],
options={ py2exe: {packages: [encodings, 'rdflib']},
py2app: {argv_emulation: True,
iconfile: os.path.join('cclookup',
'resources', 'cc.icns')
}
},
)
When I try to run this with py2app, it crashes into pdb complaining
that it can't locate pkg_resources. Running the super-simplified
version of setup.py generated by py2applet builds correctly, but has
the following problems:
* dependencies aren't included (I'm not sure if py2app actually
attempts to scan for them like py2exe or not, so this may not be
py2app's fault in the least)
* app.py is included by itself, as opposed to as part of the package.
I think that ideally I'd be able to specify my application as a
gui_scripts entry point to setup(), and have it play nicely with the
eggs specified in install_requires. I saw the docs mentioned that a
future version would use eggs (I think it was in reference to
recipes), and I was wondering what the status of that effort is.
Thanks,
Nathan
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] Interesting use of Python and Django on the Mac
This is the start of a trend we are going to see more and more of: the covergence of Web and Desktop or Web-top. Dashboard/Konfabulator were the first big step, with Slingshot and Apollo the next big one. Granted this is pre-alpha code, but one can start imagining the possibilities. http://jerakeen.org/blog/2007/03/djangokit/ ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac
Great possibilities, but I think the most important component (and the component he's not touching yet) is sync. IMO, the coolest feature of Slingshot is that Joyent provides (or will provide...) the developer with a framework that abstracts away dealing with sync offline data. Web apps and desktop apps both have there advantages and disadvantages: - with web apps, you can access your data from any where... - ...except when there's no internet...which is where desktop apps come out on top, except for the fact that your data is locked into one location - desktop apps also 'feel' nicer, and are integrated with the OS What I would love to see is a Python framework that integrates with Django, enables PyObjC apps to use Django models for data storage, with sync to a remote DB . I.e. the data is stored both locally and remotely, with sync between the two. Having the webapp UI would be useful for many applications, but I think a native UI would have advantages too. Tom On 29-Mar-07, at 2:00 PM, Daniel Lord wrote: This is the start of a trend we are going to see more and more of: the covergence of Web and Desktop or Web-top. Dashboard/Konfabulator were the first big step, with Slingshot and Apollo the next big one. Granted this is pre-alpha code, but one can start imagining the possibilities. http://jerakeen.org/blog/2007/03/djangokit/ ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
