Originally by: CCP Tuxford

---

my bad. Rest assured I'm being ridiculed by my co-workers.

---

Originally by: Jocliutzak

---

I know right but overall the changes don't seem so impressive. The significant thing is that there will be no more updates to the 2.X platform and all users of 2.X will only receive minor bug fixes. Essentially they want everyone to move to 3.X sooner rather then later. Which I don't think will be a smooth transition at all with things as they are.

---

Originally by: CCP Tuxford

---

my bad. Rest assured I'm being ridiculed by my co-workers.

---

Originally by: CCP Fallout

---

More information regarding Python 2.7 will be coming in a blog early next week, actually.

---

Originally by: CCP Tuxford

---

my bad. Rest assured I'm being ridiculed by my co-workers.

---

Originally by: Lalitah My

---

the problem with python how many versions are even released, cant make a ferrari out of a volkswagen,

but the real problem ccp suffers is the neverending queries of a sql database, its slow, has 2 times redundant query routines, its microsoft

looking forward in 17 months ow to fix that, my beliefs are perhaps limited but we will see

---

Originally by: CCP Dropbear

---

rofl

edit: ah crap, dev account. Oh well, official rofl at you sir.

---

Originally by: CCP Fallout

---

More information regarding Python 2.7 will be coming in a blog early next week, actually.

---

Originally by: pmchem

---

from http://docs.python.org/dev/whatsnew/2.7.html

http://bugs.python.org/issue4074 scalability improvement in list building
http://bugs.python.org/issue4688 garbage collection (memory management) speedup
http://bugs.python.org/issue5084 pickling memory+speed optimization
http://bugs.python.org/issue5670 pickling speedup when dealing with dicts
http://bugs.python.org/issue3582 windows-specific threading optimization

or maybe it's just groundwork for multicore programming since all the python parallel programming related toys tend to do their development with recent releases of python, e.g. http://mpi4py.scipy.org/

---

Originally by: stoicfaux

---

I know Python is used in the client, but I just can't imagine Python being used on the server side, so I wouldn't think that performance was a major reason for upgrading.

---

Originally by: stoicfaux

---

I know Python is used in the client, but I just can't imagine Python being used on the server side, so I wouldn't think that performance was a major reason for upgrading.

---

Originally by: Mr LaForge

---

Their entire codebase needs to become C++. Its more stable and its faster. And if they rewrite it then we can finally stop kicking the POS dead horse.

---

Originally by: CCP Tuxford

---

my bad. Rest assured I'm being ridiculed by my co-workers.

---

Originally by: Mr LaForge

---

Their entire codebase needs to become C++.

---

Quote:

---

Aedun Sole > flying with lyk is like flying a bus filled with 5 year old children

---

Originally by: Xessej

---

It's kind of amazing that the original designer(s) thought an interpreted scripting language was the way to go in developing a MMO.

---

Originally by: Xessej

---

At this point it is way past time that all new code be in C++ and some team be chugging away at converting the codebase. Unfortunately they seem attached to Python which means they will never achieve the performance they could get.

---

Originally by: Mr LaForge

---

Their entire codebase needs to become C++. Its more stable and its faster. And if they rewrite it then we can finally stop kicking the POS dead horse.

---

Originally by: Mr LaForge

---

Its more stable and its faster.

---

Originally by: Mr LaForge

---

Its more stable

---

Originally by: Mr LaForge

---

more stable

---

Originally by: Mr LaForge

---

more stable

---

Originally by: Mr LaForge

---

stable

---

#include <vector>
#include <iostream>
#include <sstream>
#include <algorithm>
#include <string>

using namespace std;

int is_palindrome(int possible_answer);

int main(int argc, char ** argv)
{
 vector<int> answers;
 for (int possible_answer = 100 * 100; possible_answer < 999 * 999; ++possible_answer) {
 for (int possible_divisor = 100; possible_divisor < 999; ++possible_divisor) {
 if (
 possible_answer / possible_divisor >= 100
 && possible_answer / possible_divisor <= 999
 && possible_answer % possible_divisor == 0
 && is_palindrome(possible_answer)
 ) {
 answers.push_back(possible_answer);
 }
 }
 }

 cout << "The palindrome is " << *max_element(answers.begin(), answers.end()) << endl;

 return EXIT_SUCCESS;
}

int is_palindrome(int possible_answer)
{
 string first_half, second_half;
 ostringstream ostr;
 ostr << possible_answer;

 if (ostr.str().length() % 2 != 0)
 return 0;

 first_half = ostr.str().substr(0, ostr.str().length() / 2);
 second_half = ostr.str().substr(ostr.str().length() / 2, ostr.str().length());

 reverse(second_half.begin(), second_half.end());

 if (first_half == second_half)
 return 1;
 else
 return 0;
}

def construct_palindrome(n):
s = str(n)
return int(s + s[::-1])

def is_divisible_by_three_digit_numbers(n):
for x in range(999, 100, -1):
div, mod = divmod(n, x)
if mod == 0 and div < 1000 and div >= 100:
return True
return False

for n in range(999, 100, -1):
pal = construct_palindrome(n)
if is_divisible_by_three_digit_numbers(pal):
print(pal)
break

Originally by: Liang Nuren

---

Life is about more than your programming language's speed. Its also about how it encourages you to think about problems and how easy it is to maintain.

---

Originally by: AccesiViale

---

So ... well planned and executed OO C++ would def be the better route ...

---

Quote:

---

edit: lol liang i wonder how many peoples eyes glaze over at the beginning of your code sections post before they skip to the bottom and hit reply...or simply avoid this thread all together

---

Originally by: Lalitah My

---

the problem with python how many versions are even released, cant make a ferrari out of a volkswagen,

but the real problem ccp suffers is the neverending queries of a sql database, its slow, has 2 times redundant query routines, its microsoft

looking forward in 17 months ow to fix that, my beliefs are perhaps limited but we will see

---

Originally by: Liang Nuren

---

A bunch of BS-Liang

Ed: code tags. Also, I don't claim either implementation is necessarily great - in fact I deliberately did a bad job with C++ to illustrate my point.

---

Originally by: Xessej

---

You intentionally wrote bad code as if that would prove anything. Any code you can write in Python I can write in C++ and it will run faster (Python is written in C++ and is typeless so it has to produce less efficient code than well written C++ that is a simple fact.)

---

#include <fstream>

using namespace std;

int main(int argc, char ** argv)
{
 ofstream of("output_file.txt", ios::out);
 for (int i = 0; i < 1000000; ++i)
 of << i << endl;
 of.close();
 return EXIT_SUCCESS;
}

fp = file('output_file.txt', 'w')
for x in range(1000000):
 fp.write("%d\n" % x)
fp.close()

Originally by: HenkieBoy

---

Oracle being the only real other option, they suck. Their product may be good but they are really bad for any company. They ask bucket loads of money for even the most trival options.

---

Originally by: Liang Nuren

---

Edited by: Liang Nuren on 18/08/2010 05:42:41

Originally by: Xessej

---

You intentionally wrote bad code as if that would prove anything. Any code you can write in Python I can write in C++ and it will run faster (Python is written in C++ and is typeless so it has to produce less efficient code than well written C++ that is a simple fact.)

---

Congratulations for completely missing the point. See, the point was that its all about the algorithm. People say "Switch to C++!" like its some magic cure-all but the truth of the matter is that its likely to be an enormous time investment for very little performance gain - if any. And that argument totally neglects how easy it is to maintain one over the other.

---