Graham, welcome. Careful, though -- we might convert you. ;-)
Graham. We all appreciate your expertise here and appreciate people
who say what they think. Perhaps diplomacy is not our strength. You do
not need to justify your tweet. I though it was funny because - in my
view - it would apply equally well to some of the other frameworks.
On Jan 9, 12:24 am, Graham Dumpleton <graham.d...@gmail.com>
You guys really just got to learn to do your own thing and not treating it like a crusade where you have to convert the world.
Django became popular on technical merit and because of easily accessible good documentation, not because its community went around like <insert name of church group> knocking on doors trying to convert people or arguing every little minor technical point to try and win people other. That sort of behaviour really reminds me of some new age christians I have known in the past who just could not shut up in trying to make you believe what they believed.
...if you think the latest outburst about imports was some reaction about web2py getting a tutorial accepted in PyCon as some like to think, you are very sadly mistaken. They are more likely just a manifestation of this frustration of having web2py shoved in your face one too many times especially when muds gets thrown in your direction.
So, it definitely isn't in my mind suitable for all situations.
Never done any stresstests, I'll try later to day.
Kenneth
----- Ursprungsmeddelande -----
Kenneth
You mentioned that you're using Debian Lenny. What version of Python? 2.5.2?
And what version of psycopg2?
On Feb 10, 2011, at 11:18 AM, VP <vtp...@gmail.com> wrote:
> The modules I used are all standard via installation with apt-get.
>
> Python is 2.5.2, and psycopg2 is 2.0.7
>
Upgrade psycopg2 to at least 2.0.8 and see if that doesn't fix the fault.
psycopg2 2.0.7 is the version in use in this case. 2.0.8 had this in the change log:
> * psycopg/pqpath.c (_pq_fetch_tuples): Don't call Python APIs
> without holding the GIL.
Suggestive, no? There's some evidence on the web that this may have led to "Segmentation fault - premature end of script headers" errors.
2.3.2 is current.
Thanks, Luis.
Yes, it's a useful data point.
The best test will be to have an environment that actually fails with psycopg2 2.0.7, and have the failure disappear with an updated version (and no other changes), and to get the error back again with 2.0.7.
Greetings.I have tried to replicate the error and have had noexicto.
I'm not using it myself; I'm not sure what triggers the error. I assume that there's more information earlier in this thread.
db = DAL("postgres://postgres:Error Snapshot :
<type 'exceptions.RuntimeError'>(Failure to connect, tried 5 times:
global name 'psycopg2' is not defined)
It need only be symbolic; I think that this falls into the "known bug" category. I found it by Googling.
To be more certain, it'd be good if someone could revert psycogpg2 (with no other changes) and reproduce the problem.
Thanks for the report.
I wonder if it might be worth a warning message if an app actually uses (not just imports) psycopg2 and the version is 2.0.7 or earlier. It seems to be fairly widespread.
It'd be useful to know whether it's stable at 80MB or it keeps growing.
Problem solved:
{{ #---- (CSS) -----) import random response.files.append(URL('static','css/menu.css')) response.files.append(URL('static','css/home.css')) #---- (JavaScript) --- response.files.append(URL('static','js/ajquery.scrollTo-min.js')) response.files.append(URL('static','js/bjquery.localscroll-1.2.7-min.js')) response.files.append(URL('static','js/zexamples.scroll.js')) #------ include web2py specific js code (jquery, calendar, form stuff) ------ }} {{include 'web2py_ajax.html'}} {{=toggle_menuclass()}}
{{=response.flash or ''}}{{include}} {{block sidebar}}{{end}}© 2010 by Massimo Di Pierro
# Download : hg clone https://web2py.googlecode.com/hg/ web2py
# Follow the instructions:
Title : Using psycopg2 with virtualenv on Ubuntu
Link: http://www.saltycrane.com/blog/2009/07/using-psycopg2-virtualenv-ubuntu-jaunty/
Check your syntax :
# db = DAL('postgres://myself:myp...@127.0.0.1:5432/mydatabase')
Enjoy it!
Follow the instructions:
On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:You guys really just got to learn to do your own thing and not treating it like a crusade where you have to convert the world.But that's exactly the problem -- web2py is trying to do its own thing,
and there is a vocal clique of "Pythonistas" who don't like that thing and want to stop it.
On Monday, January 10, 2011 6:36:18 AM UTC+2, Anthony wrote:On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:You guys really just got to learn to do your own thing and not treating it like a crusade where you have to convert the world.But that's exactly the problem -- web2py is trying to do its own thing,...so far so good...and there is a vocal clique of "Pythonistas" who don't like that thing and want to stop it....and here we get it wrong. Why should we care about this vocal clique?
Why should we care how many users we have?
The best, and IMO only real way to promote web2py is to facilitate the building of awesome websites. That is the whole ball game, so let's focus on that.
On Friday, July 8, 2011 3:25:45 AM UTC-4, cjrh wrote:On Monday, January 10, 2011 6:36:18 AM UTC+2, Anthony wrote:On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:You guys really just got to learn to do your own thing and not treating it like a crusade where you have to convert the world.But that's exactly the problem -- web2py is trying to do its own thing,...so far so good...and there is a vocal clique of "Pythonistas" who don't like that thing and want to stop it....and here we get it wrong. Why should we care about this vocal clique?
Note, the unfounded criticisms are effectively impugning both the technical and personal integrity of web2py's developers and users, in very public forums. This can have negative professional (and personal) consequences. If you have chosen to build an app with web2py and your client, manager, or investor reads bad things about web2py, you may lose their confidence and favor.
Why should we care how many users we have?Again, this is not the most important thing, but the number of users is not entirely without consequence either. Generally, more users will translate into more expert contributors and volunteers, which will contribute to the development of the framework and its ecosystem and to its long-term sustainability (i.e., more features, better testing and performance, better documentation, more plugins and applications, better support, more third-party hosting and development tool support, etc.).
In many cases, when you select a framework, you want some confidence that it will still be actively maintained several years hence, and that confidence will be bolstered if there is a sizable and active community around it.
Why should we care how many users we have?Again, this is not the most important thing, but the number of users is not entirely without consequence either. Generally, more users will translate into more expert contributors and volunteers, which will contribute to the development of the framework and its ecosystem and to its long-term sustainability (i.e., more features, better testing and performance, better documentation, more plugins and applications, better support, more third-party hosting and development tool support, etc.).This is almost definitely not true. Or rather, it certainly hasn't been my experience anyway. The number of people in a project or community appears to have no bearing whatsoever on the quality of the code or the abilities of contributors.
In many cases, when you select a framework, you want some confidence that it will still be actively maintained several years hence, and that confidence will be bolstered if there is a sizable and active community around it.I still don't see why this is my problem, or indeed even yours, or anyone else's for that matter. I do not see why I need to care about whether some pointy-hair boss thinks web2py will be actively maintained in the future. I have selected web2py on technical merit. I do not care how active the community is, for I have the source code.
In truth, I have selected web2py because my value system around coding has a large intersection with Massimo's, IMO. I value the conveniences that he built into web2py early on; conveniences that other frameworks left "as an exercise to the reader". I think that matters. I think that remains a selling point for web2py.
But our PR face is way, way too defensive. I understand that we might not see it like that, but if someone like Graham happens point out that that is how it looks from the outside, then we should take note of that.
You need to think slightly bigger than your own personal projects.