Opened 8 years ago

Closed 8 years ago

#5465 closed (invalid)

Summer of Code 2007: Reusable Django applications

Reported by: jezdez Owned by: jezdez
Component: Core (Other) Version: master
Severity: Keywords: packaging, sprintsept14, feature
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

As one result of my work during the Google summer of code 2007 I changed django.core.management a little and added a new django.utils.package with a metadata assistent and setuptools-based application creation. For more detail ping me on IRC (jezdez) or look at http://jannisleidel.com/ and http://groups.google.com/group/django-developers/browse_thread/thread/bc830d718957beb8

Attachments (2)

django-package.diff (31.5 KB) - added by jezdez 8 years ago.
django-package2.diff (31.5 KB) - added by jezdez 8 years ago.
changed the order of the subcommands and options in the docs, following a backwards incompatible change from #6075 (http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django-admin.pyandmanage.pynowrequiresubcommandstoprecedeoptions)

Download all attachments as: .zip

Change History (10)

Changed 8 years ago by jezdez

comment:1 Changed 8 years ago by jezdez

  • Has patch set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 8 years ago by anonymous

  • Keywords sprintsept14 added

comment:3 Changed 8 years ago by Rob Hunter <robertjhunter@…>

I love the concept. I'm not sure about the effect on tutorial-followers.

An instruction to run manage startapp polls makes enough sense to accept at the time, and understand later. Adding a {{--noskeleton}} is confusing, although being prompted for their name and what-have-you is probably confusing too.

comment:4 Changed 8 years ago by jezdez

Yeah, unfortunately the whole "project" metaphor is quite misleading and was only introduced to make it easier for beginners to start. One effect of practice within the developer community is that most of them don't think that Django apps are also Python modules and can be used like it.

You are right, having to add --noskeleton to the tutorial is not logical - but my goal in the GSoC was to patch as little as possible of the current code base, so I dropped alternative ideas like introducing a whole new "package" command and other re-factoring possibilities. We need to tell the beginners what it means to have a distributable version of a Django application. I wonder how the usual way is to describe the use of e.g. django-tagging to a newbie?

One thing was also on my screen during the research for GSoC: setuptools and how it's used by Paste. Very nice and intuitive, but to complicated combine with Django, which implements very much itself than using an external library.

comment:5 Changed 8 years ago by Simon G. <dev@…>

  • Triage Stage changed from Unreviewed to Design decision needed

jezdez - can you raise this on django-dev?

comment:6 Changed 8 years ago by jezdez

Sure, but do you mean this specific ticket or the general topic of best practices, setuptools and tutorials?

Changed 8 years ago by jezdez

changed the order of the subcommands and options in the docs, following a backwards incompatible change from #6075 (http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django-admin.pyandmanage.pynowrequiresubcommandstoprecedeoptions)

comment:7 Changed 8 years ago by PhiR

  • Keywords feature added

comment:8 Changed 8 years ago by jacob

  • Resolution set to invalid
  • Status changed from new to closed

This is a lot bigger than a ticket. Since there isn't exactly a "next action" on this ticket, I'm going to mark it invalid while we discuss the bigger issues on django-dev.

Note: See TracTickets for help on using tickets.
Back to Top