To clarify the problems installing eggs to non-default locations:
On having to use eggs again I've discovered that this can be a problem
in that you only packages installed in "site" directories (such as
site-packages) can be autoloaded. Prior to version 0.6a1 ez_install
did not recognize that m
On thinking about it the problems were with easy install's use of .pth
files rather than with eggs - only ever having used eggs in combination
with easy install I'm almost certainly thinking of that.
Nick
On 9/15/05, nichyoung <[EMAIL PROTECTED]> wrote:
> There are some issues with the Python Egg sys.path magic where
> installing somewhere other than the default python path (eg:
> usr/lib/python2.x/site-packages).
Hmm... Okay.
I've never had any problems, with the eggs I've used. And I installed
There are some issues with the Python Egg sys.path magic where
installing somewhere other than the default python path (eg:
usr/lib/python2.x/site-packages). That's probably a fairly common
requirement for Django users on shared hosting so using standard .eggs
might not be the best solution.
Nic
On 9/13/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> or may not be good in the long term. Personally, I think it would be
> cool to load apps from ZIP files (like JARs) so that an app is a
> single package...
Or Python Eggs; which are zip-files named .egg, with some
machinery for getting d
> - We need to fix on a good structure for app packages. As a few
> people have mentioned, the one that django-admin startapp creates may
> or may not be good in the long term. Personally, I think it would be
> cool to load apps from ZIP files (like JARs) so that an app is a
> single pac
On Sep 12, 2005, at 9:07 PM, [EMAIL PROTECTED] wrote:
What if we, the community, created our own site. djangoapps.com or
something. It would allow people to upload there own django apps.
People could rate and comment on the apps posted there. And it would
of course be written using django.
What if we, the community, created our own site. djangoapps.com or
something. It would allow people to upload there own django apps.
People could rate and comment on the apps posted there. And it would
of course be written using django.
On Thu, 2005-09-08 at 19:21 -0700, Jason Huggins wrote:
> Jason F. McBrayer wrote:
> > Hi. I've more-or-less finished a django app that might be useful to
> > other people
>
> > I'd like to package this for other people in a way that is as convenient
> > for them as possible, while not requiring
Jason F. McBrayer wrote:
> Hi. I've more-or-less finished a django app that might be useful to
> other people
> I'd like to package this for other people in a way that is as convenient
> for them as possible, while not requiring too much work from me. So,
> what do people expect from a third-pa
Hi. I've more-or-less finished a django app that might be useful to
other people --- it's a feed reader similar to feedonfeeds, except that
it is multiuser, supports categories, and is more tolerant of invalid
feeds (thanks to the wonderful feedparser -- feedparser.org). It's
basically functiona
11 matches
Mail list logo
