[Python-Dev] Status of MS Windows CE port

2008-09-23 Thread Ulrich Eckhardt 
Greetings!

I'm currently trying to assess the effort required for a CE port. I'm already 
aware of the project at http://pythonce.sourceforge.net, but I find it a 
waste of time to have two separate projects which then require syncing 
changes back and forth.

Questions:
- What are the feelings towards a port in the mainline? I'm aware that you are 
trying to get 2.6 and 3.0 out of the door and are probably not willing to 
risk such changes to the release code right now, but in general?
- Is anyone already working on this? I know that Brad Clements made an attempt 
some years ago but didn't get it integrated, are there any others? Maybe even 
any ongoing work?
- I see that you are using Subversion and Bazaar, would it be possible to get 
a feature branch for the CE port? I'm thinking about the effort going on at 
pythonce.sf.net and some further porting that I need for my specific 
platform. IMHO both would be better off in the same repository as your 
upstream sources, since merging changes back and forth is much easier that 
way.

Thanks!

Uli

-- 
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.

**

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Status of dictnotes.txt?

2008-09-23 Thread Brendan O'Connor 
> If I remember correctly (and based on a skimming of dictnotes.txt),
> those aren't suggestions, it is documentation about the actual
> implementation and why those decisions were made.

Well, some of the document is written as "if we did X, then we'd see
Y" so it's not always clear.  Some parts are clearly not implemented,
e.g. read-only freezing.  Some parts are implemented but slightly
differently -- e.g. small dicts are specialized to be faster, but the
document talks about specializing lookdict() and lookdict_string()
with linear search; however, as far as I can tell,
PyDictObject->ma_smalltable is used for small dictionaries, with the
standard hashing algorithm.

This is a little confusing because the ma_lookup() function pointer is
used as indirection; I was thinking that maybe there was a linear
search version, but actually it looks like it's just set to
lookdict_string() then switches to lookdict() if there's ever a
non-string key.  lookdict[_string]() always uses hashing.

Anyway, if anyone who knows about this or dictnotes.txt in general is
reading, feel free to pipe in :)

Brendan
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] okay to add new test cases to 2.6?

2008-09-23 Thread skip 
Benjamin Peterson wound up writing a test case for the new C atexit module
on the py3k branch.  A similar test, though different in detail, makes sense
for the Python atexit module on trunk.  Is this something I can check in or
should I just wait until after 2.6 is released?

def test_badargs(self):
s = StringIO.StringIO()
sys.stdout = sys.stderr = s
save_handlers = atexit._exithandlers
atexit._exithandlers = []
try:
atexit.register(lambda: 1, 0, 0, (x for x in (1,2)), 0, 0)
self.assertRaises(TypeError, atexit._run_exitfuncs)
finally:
sys.stdout = sys.__stdout__
sys.stderr = sys.__stderr__
atexit._exithandlers = save_handlers

Thx,

Skip
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] okay to add new test cases to 2.6?

2008-09-23 Thread Barry Warsaw 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sep 23, 2008, at 4:00 PM, [EMAIL PROTECTED] wrote:

Benjamin Peterson wound up writing a test case for the new C atexit  
module
on the py3k branch.  A similar test, though different in detail,  
makes sense
for the Python atexit module on trunk.  Is this something I can  
check in or

should I just wait until after 2.6 is released?

   def test_badargs(self):
   s = StringIO.StringIO()
   sys.stdout = sys.stderr = s
   save_handlers = atexit._exithandlers
   atexit._exithandlers = []
   try:
   atexit.register(lambda: 1, 0, 0, (x for x in (1,2)), 0, 0)
   self.assertRaises(TypeError, atexit._run_exitfuncs)
   finally:
   sys.stdout = sys.__stdout__
   sys.stderr = sys.__stderr__
   atexit._exithandlers = save_handlers


If you don't increase the redness of the buildbots, I think it's fine.

- -Barry

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSNlSHXEjvBPtnXfVAQKQ3gP/XJr97CdjZitwSQxrL28xCuLyPfKmtBVA
2hK2ewQxH9Rxrl0BsFZlnBz2vEygPmPWnduu8VT+sjsrFu/Ua9d1Xo06lQ6/fFck
Tp/en0KlAyJ6Pjf/1pWahn4ttwk74YG02LiQgUsfOaIUG+8cMfGfrtyUzwGBoKhW
4RBuwpPjsBo=
=7Brm
-END PGP SIGNATURE-
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Status of MS Windows CE port

2008-09-23 Thread Neal Norwitz 
On Tue, Sep 23, 2008 at 1:52 AM, Ulrich Eckhardt
<[EMAIL PROTECTED]> wrote:
> Greetings!
>
> I'm currently trying to assess the effort required for a CE port. I'm already
> aware of the project at http://pythonce.sourceforge.net, but I find it a
> waste of time to have two separate projects which then require syncing
> changes back and forth.
>
> Questions:
> - What are the feelings towards a port in the mainline? I'm aware that you are
> trying to get 2.6 and 3.0 out of the door and are probably not willing to
> risk such changes to the release code right now, but in general?

In general, we try to ensure that there is an active maintainer,
preferably more than one.  As long as it doesn't make the code that
much harder to maintain, it is desirable to support more platforms.

> - Is anyone already working on this? I know that Brad Clements made an attempt
> some years ago but didn't get it integrated, are there any others? Maybe even
> any ongoing work?

I'm not sure if anyone here knows.  I haven't seen anything on this
list, but that doesn't mean there isn't another list either on
python.org or elsewhere that does have the information.  Try searching
if you haven't.

> - I see that you are using Subversion and Bazaar, would it be possible to get
> a feature branch for the CE port? I'm thinking about the effort going on at
> pythonce.sf.net and some further porting that I need for my specific
> platform. IMHO both would be better off in the same repository as your
> upstream sources, since merging changes back and forth is much easier that
> way.

It's possible.  The best way to get the ball rolling is to produce
some patches against the mainline.  Demonstrate what you can do and
privileges will follow.  It's a similar process to becoming a
python-committer.

Perhaps the best way to start is using Bazaar or some distributed
version control system for your patches.  Once you've demonstrated
your ability and intent, we can make a branch.

Cheers,
n
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] json decoder speedups, any time left for 2.6?

2008-09-23 Thread Bob Ippolito 
I'm out of town this week for a conference (ICFP/CUFP in Victoria) and
my hotel's connection has been bad enough such that I can't get any
Real Work done so I've managed to hammer on the json library's
decoding quite a bit instead. I just released simplejson 1.9.3 which
improves decoding performance by about 2x and I've got some more
changes along the way in trunk for 1.9.4 that will increase it even
further (over 3x my original 1.9.2 benchmark perf). How much time do I
have left to get this into Python 2.6?

FWIW the changes are all on the Python side, no C code has been harmed
(yet). The test suite still passes of course.

-bob
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com