Message5292
Well, I see two options
1. Determine what the actual behaviour is for option inheritance in
cpython for all options on all platforms, then
- See if there is identical behaviour on all platforms (that we care
about).
- If option inheritance is identical on all platforms, implement it on
jython
- If it is not, then things stay as they are
2. Implement an optional jython-specific method which
- Permits the user to specify which options they wish to have inherited
- Must be explicitly called by the user to take effect
Number 1 should not be too hard to investigate (and implement), as long
as I can get collaborators to run some cpython code I'll write, on all
the platforms we care about, and report back the results.
My gut feeling says we should go with option 2. This is a similar option
to what I did with select.cpython_compatible_select. |
|
Date |
User |
Action |
Args |
2009-10-28 21:26:41 | amak | set | messageid: <1256765201.33.0.799059849551.issue1309@psf.upfronthosting.co.za> |
2009-10-28 21:26:41 | amak | set | recipients:
+ amak, fwierzbicki, pjenvey, tercero12 |
2009-10-28 21:26:41 | amak | link | issue1309 messages |
2009-10-28 21:26:41 | amak | create | |
|