Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
1.0

1.0

Ratings: (0)|Views: 0 |Likes:
Published by Michael Shonukan

More info:

Published by: Michael Shonukan on Mar 25, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as TXT, PDF, TXT or read online from Scribd
See more
See less

07/18/2014

pdf

text

original

 
========================Django1.0releasenotes========================WelcometoDjango1.0!We'vebeenlookingforwardtothismomentforoverthreeyears,andit'sfinallyhere.Django1.0representsathelargestmilestoneinDjango'sdevelopmenttodate:aWebframeworkthatagroupofperfectionistscantrulybeproudof.Django1.0representsoverthreeyearsofcommunitydevelopmentasanOpenSourceproject.Django'sreceivedcontributionsfromhundredsofdevelopers,beentranslatedintofiftylanguages,andtodayisusedbydevelopersoneverycontinentandineverykindofjob.Aninterestinghistoricalnote:whenDjangowasfirstreleasedinJuly2005,theinitialreleasedversionofDjangocamefromaninternalrepositoryatrevisionnumber8825.Django1.0representsrevision8961ofourpublicrepository.Itseemsfittingthatour1.0releasecomesatthemomentwherecommunitycontributionsovertakethosemadeprivately.Stabilityandforwards-compatibility====================================:doc:`ThereleaseofDjango1.0</releases/1.0>`comeswithapromiseofAPIstabilityandforwards-compatibility.Inanutshell,thismeansthatcodeyoudevelopagainstDjango1.0willcontinuetoworkagainst1.1unchanged,andyoushouldneedtomakeonlyminorchangesforany1.Xrelease.Seethe:doc:`APIstabilityguide</misc/api-stability>`forfulldetails.Backwards-incompatiblechanges==============================Django1.0hasanumberofbackwards-incompatiblechangesfromDjango0.96.IfyouhaveappswrittenagainstDjango0.96thatyouneedtoport,seeourdetailedportingguide:..toctree:::maxdepth:11.0-porting-guideAcompletelistofbackwards-incompatiblechangescanbefoundathttp://code.djangoproject.com/wiki/BackwardsIncompatibleChanges.What'snewinDjango1.0========================A*lot*!SinceDjango0.96,we'vemadeover4,000codecommits,fixedmorethan2,000bugs,andedited,added,orremovedaround350,000linesofcode.We'vealsoadded40,000linesofnewdocumentation,andgreatlyimprovedwhatwasalreadythere.Infact,newdocumentationisoneofourfavoritefeaturesofDjango1.0,sowemightaswellstartthere.First,there'sanewdocumentationsite:http://docs.djangoproject.com/
 
Thedocumentationhasbeengreatlyimproved,cleanedup,andgenerallymadeawesome.There'snowdedicatedsearch,indexes,andmore.Wecan'tpossiblydocumenteverythingthat'snewin1.0,butthedocumentationwillbeyourdefinitiveguide.Anywhereyouseesomethinglike:..versionadded::1.0ThisfeatureisnewinDjango1.0You'llknowthatyou'relookingatsomethingneworchanged.TheothermajorhighlightsofDjango1.0are:Re-factoredadminapplication-----------------------------TheDjangoadministrativeinterface(``django.contrib.admin``)hasbeencompletelyrefactored;admindefinitionsarenowcompletelydecoupledfrommodeldefinitions(nomore``classAdmin``declarationinmodels!),rewrittentouseDjango'snewform-handlinglibrary(introducedinthe0.96releaseas``django.newforms``,andnowavailableassimply``django.forms``)andredesignedwithextensibilityandcustomizationinmind.FulldocumentationfortheadminapplicationisavailableonlineintheofficialDjangodocumentation:Seethe:doc:`adminreference</ref/contrib/admin/index>`fordetailsImprovedUnicodehandling-------------------------Django'sinternalshavebeenrefactoredtouseUnicodethroughout;thisdrasticallysimplifiesthetaskofdealingwithnon-Western-EuropeancontentanddatainDjango.Additionally,utilityfunctionshavebeenprovidedtoeaseinteroperabilitywiththird-partylibrariesandsystemswhichmayormaynothandleUnicodegracefully.DetailsareavailableinDjango'sUnicode-handlingdocumentation.See:doc:`/ref/unicode`.AnimprovedORM---------------Django'sobject-relationalmapper--thecomponentwhichprovidesthemappingbetweenDjangomodelclassesandyourdatabase,andwhichmediatesyourdatabasequeries--hasbeendramaticallyimprovedbyamassiverefactoring.FormostusersofDjangothisisbackwards-compatible;thepublic-facingAPIfordatabasequeryingunderwentafewminorchanges,butmostoftheupdatestookplaceintheORM'sinternals.Aguidetothechanges,includingbackwards-incompatiblemodificationsandmentionsofnewfeaturesopenedupbythisrefactoring,is`availableontheDjangowiki`__. __http://code.djangoproject.com/wiki/QuerysetRefactorBranchAutomaticescapingoftemplatevariables----------------------------------------Toprovideimprovedsecurityagainstcross-sitescripting(XSS)vulnerabilities,Django'stemplatesystemnowautomaticallyescapestheoutputofvariables.Thisbehaviorisconfigurable,andallowsbothvariablesandlargertemplateconstructstobemarkedassafe(requiringnoescaping)orunsafe(requiring
 
escaping).Afullguidetothisfeatureisinthedocumentationforthe:ttag:`autoescape`tag.``django.contrib.gis``(GeoDjango)----------------------------------Aprojectoverayearinthemaking,thisaddsworld-classGIS(`GeographicInformationSystems`_)supporttoDjango,intheformofa``contrib``application.Itsdocumentationiscurrentlybeingmaintainedexternally,andwillbemergedintothemainDjangodocumentationshortly.HugethanksgotoJustinBronn,JeremyDunck,BrettHoernerandTravisPinneyfortheireffortsincreatingandcompletingthisfeature.Seehttp://geodjango.org/fordetails..._GeographicInformationSystems:http://en.wikipedia.org/wiki/Geographic_information_systemPluggablefilestorage----------------------Django'sbuilt-in``FileField``and``ImageField``nowcantakeadvantageofpluggablefile-storagebackends,allowingextensivecustomizationofwhereandhowuploadedfilesgetstoredbyDjango.Fordetails,see:doc:`thefilesdocumentation</topics/files>`;bigthanksgotoMartyAlchinforputtinginthehardworktogetthiscompleted.Jythoncompatibility--------------------ThankstoalotofworkfromLeoSotoduringaGoogleSummerofCodeproject,Django'scodebasehasbeenrefactoredtoremoveincompatibilitieswith`Jython`_,animplementationofPythonwritteninJava,whichrunsPythoncodeontheJavaVirtualMachine.DjangoisnowcompatiblewiththeforthcomingJython2.5release.See:doc:`/howto/jython`..._Jython:http://www.jython.org/Genericrelationsinformsandadmin------------------------------------Classesarenowincludedin``django.contrib.contenttypes``whichcanbeusedtosupportgenericrelationsinboththeadmininterfaceandinend-userforms.See:ref:`thedocumentationforgenericrelations<generic-relations>`fordetails.``INSERT``/``UPDATE``distinction---------------------------------AlthoughDjango'sdefaultbehaviorofhavingamodel's``save()``methodautomaticallydeterminewhethertoperforman``INSERT``oran``UPDATE``attheSQLlevelissuitableforthemajorityofcases,thereareoccasionalsituationswhereforcingoneortheotherisuseful.Asaresult,modelscannowsupportanadditionalparameterto``save()``whichcanforceaspecificoperation.See:ref:`ref-models-force-insert`fordetails.Split``CacheMiddleware``-------------------------

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->