On 6/19/2013 4:03 AM, Wolfgang Maier wrote:
Wolfgang Maier biologie.uni-freiburg.de> writes:
andrea crotti gmail.com> writes:
2013/6/18 Terry Reedy udel.edu>
Decorators are only worthwhile if used repeatedly. What you specified can
easily be written, for instance, as
def save_doc(db=No
Wolfgang Maier biologie.uni-freiburg.de> writes:
>
> andrea crotti gmail.com> writes:
>
> > 2013/6/18 Terry Reedy udel.edu>
> >
> > Decorators are only worthwhile if used repeatedly. What you specified can
> easily be written, for instance, as
> > def save_doc(db=None):
> > if db is None:
andrea crotti gmail.com> writes:
>
> 2013/6/18 Terry Reedy udel.edu>
> On 6/18/2013 5:47 AM, andrea crotti wrote:
> Using a CouchDB server we have a different database object potentially
> for every request.
> We already set that db in the request object to make it easy to pass it
> around for
On Tue, 18 Jun 2013 10:47:57 +0100, andrea crotti wrote:
> Using a CouchDB server we have a different database object potentially
> for every request.
>
> We already set that db in the request object to make it easy to pass it
> around form our django app, however it would be nice if I could set
2013/6/18 Terry Reedy
> On 6/18/2013 5:47 AM, andrea crotti wrote:
>
>> Using a CouchDB server we have a different database object potentially
>> for every request.
>>
>> We already set that db in the request object to make it easy to pass it
>> around form our django app, however it would be nic
On 6/18/2013 5:47 AM, andrea crotti wrote:
Using a CouchDB server we have a different database object potentially
for every request.
We already set that db in the request object to make it easy to pass it
around form our django app, however it would be nice if I could set it
once in the API and
andrea crotti gmail.com> writes:
>
> 2013/6/18 Wolfgang Maier biologie.uni-freiburg.de>
>
>
> andrea crotti gmail.com> writes:
> >
> >
> > Using a CouchDB server we have a different database object potentially for
> every request.
> >
> > We already set that db in the request object to make
2013/6/18 Wolfgang Maier
> andrea crotti gmail.com> writes:
>
> >
> >
> > Using a CouchDB server we have a different database object potentially
> for
> every request.
> >
> > We already set that db in the request object to make it easy to pass it
> around form our django app, however it would b
andrea crotti gmail.com> writes:
>
>
> Using a CouchDB server we have a different database object potentially for
every request.
>
> We already set that db in the request object to make it easy to pass it
around form our django app, however it would be nice if I could set it once
in the API an
On Tue, Jun 18, 2013 at 10:47 AM, andrea crotti
wrote:
> def with_optional_db(func):
> """Decorator that sets the database to the global current one if
> not passed in or if passed in and None
> """
> @wraps(func)
> def _with_optional_db(*args, **kwargs):
> func_args = func.func_code.co_varnames
>
Using a CouchDB server we have a different database object potentially for
every request.
We already set that db in the request object to make it easy to pass it
around form our django app, however it would be nice if I could set it once
in the API and automatically fetch it from there.
Basically
KraftDiner wrote:
> I have a question..
>
> myGlobalDictionary = dictionary()
>
>
> class someClass:
>def __init__(self):
> self.x = 0;
>def getValue(self, v)
> myGlobalDictionary.getVal(v)
>
>
> myGlobalDictionary doesn't seem to be visible to my someClass methods.
> Why?
KraftDiner wrote:
> I have a question..
>
> myGlobalDictionary = dictionary()
>
>
> class someClass:
>def __init__(self):
> self.x = 0;
>def getValue(self, v)
> myGlobalDictionary.getVal(v)
>
>
> myGlobalDictionary doesn't seem to be visible to my someClass methods.
> Why?
KraftDiner wrote:
> myGlobalDictionary doesn't seem to be visible to my someClass methods.
> Why? What should I do?
Specify more clearly what is happening, what you wanted it to do, and
why you think it's wrong? You haven't given enough information.
--
Erik Max Francis && [EMAIL PROTECTED] &
I have a question..
myGlobalDictionary = dictionary()
class someClass:
def __init__(self):
self.x = 0;
def getValue(self, v)
myGlobalDictionary.getVal(v)
myGlobalDictionary doesn't seem to be visible to my someClass methods.
Why? What should I do?
--
http://mail.python.org
Fredrik Lundh wrote:
> no, the "bar.py" *file* gets loaded twice, first as the "foo.bar"
> module, and then as the "bar" module.
True and I agree with your email, but suppose there is bar1.py and bar2.py
in foo, then they can refer to each other by importing bar2 and bar1,
respectively. These mod
Jeremy Sanders wrote:
>> if you got some other result, you didn't just import the same thing
>> twice...
>
> I think you may be incorrect, or I have misinterpreted you.
you've misinterpreted what Python means by "a module".
> Try this:
> import foo.bar
here you import the module named "foo.ba
Fredrik Lundh wrote:
> if you got some other result, you didn't just import the same thing
> twice...
I think you may be incorrect, or I have misinterpreted you.
Try this:
** In test.py
import sys
import foo.bar
print foo.bar.myvar
foo.bar.myvar = 42
print foo.bar.myvar
Got crystal clear. Thanks a lot to all for the elaborated replies.
Sanjay
--
http://mail.python.org/mailman/listinfo/python-list
Jeremy Sanders wrote:
>> "import" doesn't create new objects, so that's not very likely. can you
>> post some code so we don't have to guess what you've tried and not ?
>
> It does if you mess around with sys.path between doing two imports of the
> same thing (at least I found out the hard way o
Fredrik Lundh wrote:
> "Sanjay" wrote:
>
>> Trying hard, I am not even being able to figure out how to create an
>> object in one module and refer the same in another one. "import"
>> created a new object, as I tried.
>
> "import" doesn't create new objects, so that's not very likely. can you
>
Sanjay wrote:
> Hi Bruno,
>
> Thanks a lot for the reply. In order to post here, I wrote a very
> simple program now, and it seems working! I can diagnose the original
> problem now.
Fine.
> There might be some other problem.
This, we can't tell, since you didn't post the code !-)
> Pardon me
Sanjay wrote:
> Probably a newcomer question, but I could not find a solution.
>
> I am trying to have some singleton global objects like "database
> connection" or "session" shared application wide.
>
> Trying hard, I am not even being able to figure out h
:
"(at the module's to level)"
Thanks
Sanjay
--
Bruno Desthuilliers wrote:
> Sanjay wrote:
> > Probably a newcomer question, but I could not find a solution.
> >
> > I am trying to have some sin
"Sanjay" wrote:
> Trying hard, I am not even being able to figure out how to create an
> object in one module and refer the same in another one. "import"
> created a new object, as I tried.
"import" doesn't create new objects, so that's not very likely. can you post
some code so we don't have to
Sanjay wrote:
> Probably a newcomer question, but I could not find a solution.
>
> I am trying to have some singleton global objects like "database
> connection" or "session" shared application wide.
Whenever possible, dont. If you really have no other way out
Probably a newcomer question, but I could not find a solution.
I am trying to have some singleton global objects like "database
connection" or "session" shared application wide.
Trying hard, I am not even being able to figure out how to create an
object in one module a
27 matches
Mail list logo
