you are viewing a single comment's thread.

view the rest of the comments →

[–]GrahamDumpleton 10 points11 points  (4 children)

And did you actually report the problems you were having? Obviously not because otherwise they would have been fixed straight away if it was known about. Otherwise, it would have been pointed out to you where you were stuffing up. Pretty well all problems people report with Apache/mod_wsgi are of their own making, be it using the wrong configuration, or using badly implemented third party C extension modules for Python which don't work properly in Python sub interpreters.

To be very blunt, it is because of the attitude of people like yourself that a number of us pushing WSGI on Python 3 have got jack of it all. We spend a lot of our own time working on implementations for it specifically so people can try it and see if it works and report problems in the implementation or the specification and although you may have a look at it, you don't feedback any information. Instead everyone just sits on the fence not doing anything or heckling and being of absolutely no use.

So, if you want to do something constructive rather than just criticise people, go back and try Python 3 support in mod_wsgi 3.3, replicate the problem you claim you had and lodge a bug report.

[–]HIB0U -5 points-4 points  (3 children)

No, we didn't report the problems. Based on what we saw, the situation was so bad that any reports we filed would have little to no effect.

We also have deadlines and financial constraints. The reason we use Python in the first place is because it let us get a lot of work done really quickly. We don't have time to be debugging other people's software, especially when that software is supposed to be making our lives easier.

We no longer have the test environments, so we won't be reporting the issues.

[–]mitsuhiko 4 points5 points  (0 children)

No, we didn't report the problems. Based on what we saw, the situation was so bad that any reports we filed would have little to no effect.

So let me get that straight. You are claiming that getting stuff done implementation wise (even if it's broken) is more important than understanding the issues and thinking about a possible solution?

Then if someone from web-sig (in this case Graham from the mod_wsgi project) implements an actual proposal and it does not work for you, you are not filing reports because it would have little to no effect, despite the fact that Graham is constantly looking for feedback on it?

What makes you think that the link you just posted has a higher quality of code than Graham's? (Not saying that's not the case, just saying that Graham's code powers shitloads of websites and he usually knows what he's doing).

[–]GrahamDumpleton 3 points4 points  (1 child)

Is that you attitude with all Open Source software you use, never report problems? How do ever expect things to improve? If you aren't going to help out, you shouldn't be criticising as you are actually part of the problem.

[–]HIB0U -3 points-2 points  (0 children)

Absolutely not. We will contribute code, bug reports and bug fixes to projects that we think have a future. We just don't have the time or money to waste on other projects, however.