Many thanks Chris, the problem is solved in 1.0a6
Jerry
On Dec 16, 4:16 am, Chris McDonough wrote:
> On Wed, 2010-12-15 at 12:54 -0500, Chris McDonough wrote:
> > On Wed, 2010-12-15 at 09:50 -0800, Jerry wrote:
> > > Hi Chris,
>
> > > Upon upgrade, and after updating all "from pyramid.config imp
Yesterday's alpha (1.0a5) was a bit of a brownbag due to a bug it
introduced when "pyramid.config.Configurator.scan()" was called without
arguments. To ensure that the fewest number of people run into this
bug, I've made a 1.0a6 release with a fix.
A number of other documentation and testing impr
On Dec 15, 4:01 pm, Chris McDonough wrote:
> On Wed, 2010-12-15 at 12:55 -0800, reed wrote:
>
> > > The need for a change is mostly rationalized by this:
>
> > >http://docs.pylonshq.com/pyramid/dev/designdefense.html#pyramid-uses-...
> I think folks who prefer
> "node" (or really anything-not-r
On Wed, 2010-12-15 at 12:55 -0800, reed wrote:
>
> On Dec 15, 3:30 pm, Chris McDonough wrote:
> > On Wed, 2010-12-15 at 15:25 -0500, Chris Rossi wrote:
> > > On Wed, Dec 15, 2010 at 2:38 PM, reed wrote:
> >
> > > I am not adverse to renaming, but I think it needs to be
> > > defi
On Dec 15, 3:30 pm, Chris McDonough wrote:
> On Wed, 2010-12-15 at 15:25 -0500, Chris Rossi wrote:
> > On Wed, Dec 15, 2010 at 2:38 PM, reed wrote:
>
> > I am not adverse to renaming, but I think it needs to be
> > definitive
> > and concise enough to prevent more questi
On Wed, 2010-12-15 at 15:25 -0500, Chris Rossi wrote:
> On Wed, Dec 15, 2010 at 2:38 PM, reed wrote:
>
>
> I am not adverse to renaming, but I think it needs to be
> definitive
> and concise enough to prevent more questions from arising than
> it
>
On Wed, Dec 15, 2010 at 2:38 PM, reed wrote:
>
> I am not adverse to renaming, but I think it needs to be definitive
> and concise enough to prevent more questions from arising than it
> would solve. I don't think 'resource' meets those criteria.
>
> I tend to agree with this. I'll try to brains
On Wed, 2010-12-15 at 12:54 -0500, Chris McDonough wrote:
> On Wed, 2010-12-15 at 09:50 -0800, Jerry wrote:
> > Hi Chris,
> >
> > Upon upgrade, and after updating all "from pyramid.config import
> > Configurator", I receive many DeprecationWarning on packages that are
> > never imported in my proj
> For those folks that strongly disagree, given that some distinction
> needs to be made between "domain model" and "graph of traversable
> objects", can you think of a better term than "resource" for a node in
> that graph?
Node? Atom? And you could still define them in a 'Model'
--
You receiv
On Dec 15, 12:13 pm, Chris McDonough wrote:
> I'm considering making a fairly major terminology change to the Pyramid
> docs. I'd like to consider renaming the term "model" to "resource" in
> the docs.
-0 to renaming -1 to resource
> Why "resource"? Well, a URL is a "universal resource locat
On Wed, Dec 15, 2010 at 10:13 AM, Daniel Holth wrote:
> -1 I think the word 'resource' is at least as overloaded as the word
> 'model'.
I'm tending toward -0. Best to leave the existing terminology until a
more compelling name is found for traversal-model, one that is less
ambiguous than "model"
On Wed, Dec 15, 2010 at 12:13:05PM -0500, Chris McDonough wrote:
> I'm considering making a fairly major terminology change to the Pyramid
> docs. I'd like to consider renaming the term "model" to "resource" in
> the docs.
...
> Does anyone strongly agree or strongly disagree with this?
I'm waver
-1 I think the word 'resource' is at least as overloaded as the word
'model'.
If it's a graph it could contain nodes?
After an "aha" moment, I always thought of my bfg app as having a traversal
model /and/ a data model, with the leaves of the traversal model tending to
be SQLAlchemy mapped cla
On Wed, 2010-12-15 at 09:50 -0800, Jerry wrote:
> Hi Chris,
>
> Upon upgrade, and after updating all "from pyramid.config import
> Configurator", I receive many DeprecationWarning on packages that are
> never imported in my project (full output
> http://pylonshq.com/pasties/2bc1675b1f3718399910845
On Wed, 2010-12-15 at 17:43 +, Graham Higgins wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 15 Dec 2010, at 17:13, Chris McDonough wrote:
> > I'm considering making a fairly major terminology change to the
> > Pyramid
> > docs. I'd like to consider renaming the term "model
Hi Chris,
Upon upgrade, and after updating all "from pyramid.config import
Configurator", I receive many DeprecationWarning on packages that are
never imported in my project (full output
http://pylonshq.com/pasties/2bc1675b1f3718399910845448bfd0a8 ) --
/usr/lib/python2.6/inspect.py:252: Deprecati
On Dec 15, 2010, at 12:13 PM, Chris McDonough wrote:
> I'm considering making a fairly major terminology change to the Pyramid
> docs. I'd like to consider renaming the term "model" to "resource" in
> the docs.
My only concern would be that some folks use "resource" to refer to things like
.jss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15 Dec 2010, at 17:13, Chris McDonough wrote:
I'm considering making a fairly major terminology change to the
Pyramid
docs. I'd like to consider renaming the term "model" to "resource" in
the docs.
Does anyone strongly agree or strongly disa
+1
"Resource" is a more straightforward term when it comes to traversal.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-d
+1 for me
The name doesn't really matter that much to me but anyone learning Pyramid
from a non-zopey background will get tripped up by the usage of model imho.
- Rocky
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, se
On Wed, 2010-12-15 at 19:17 +0200, averkh...@gmail.com wrote:
> When planned release and freeze api
Our "hard" deadline is the date of PyCon US (March 11). But, depending
upon contributor schedules, we may be able to release it before then.
- C
--
You received this message because you are
+0 from my part
On Dec 15, 1:13 pm, Chris McDonough wrote:
> I'm considering making a fairly major terminology change to the Pyramid
> docs. I'd like to consider renaming the term "model" to "resource" in
> the docs.
>
> Since repoze.bfg 0.1, we've used the term "model" to refer to each
> object
When planned release and freeze api
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
Chris,
I don't strongly agree or disagree - but it seems like a +1 to me.
A
On 12/15/10 9:13 AM, "Chris McDonough" wrote:
> I'm considering making a fairly major terminology change to the Pyramid
> docs. I'd like to consider renaming the term "model" to "resource" in
> the docs.
>
> Since re
I'm considering making a fairly major terminology change to the Pyramid
docs. I'd like to consider renaming the term "model" to "resource" in
the docs.
Since repoze.bfg 0.1, we've used the term "model" to refer to each
object that forms the graph used by traversal. This is due to Pyramid's
Zope
25 matches
Mail list logo
