On Tue, Sep 04, 2012 at 02:24:10AM -0700, Andrew Svetlov wrote:
> Is it still up to date? Bug has been created in 2004.
> I don't see Tru64 in list of available buildbots.
>
> Do we need to care about this platform? And how to make sure what
> existing code works fine for that?
There's a Snak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/12 00:11, mar...@v.loewis.de wrote:
> We don't need to. It's perfectly fine if it breaks - we just can't
> actively remove code to support the platform.
>
> OTOH, if Tru64 was proposed for "unsupport", we could disable
> support in 3.4, and
Zitat von Larry Hastings :
On 09/04/2012 03:15 PM, mar...@v.loewis.de wrote:
The world wouldn't end if the test broke on Tru64, though.
FWIW, HP drops support for Tru64 at the end of this year:
http://h30097.www3.hp.com/tru64roadmap.pdf
Of course, this doesn't directly imply Python sho
On Wed, 05 Sep 2012 15:26:03 -0700
Larry Hastings wrote:
>
> On 09/04/2012 03:15 PM, mar...@v.loewis.de wrote:
> > The world wouldn't end if the test broke on Tru64, though.
>
> FWIW, HP drops support for Tru64 at the end of this year:
>
> http://h30097.www3.hp.com/tru64roadmap.pdf
>
>
>
On 09/04/2012 03:15 PM, mar...@v.loewis.de wrote:
The world wouldn't end if the test broke on Tru64, though.
FWIW, HP drops support for Tru64 at the end of this year:
http://h30097.www3.hp.com/tru64roadmap.pdf
Of course, this doesn't directly imply Python should stop supporting
it--IIRC
On Wed, Sep 5, 2012 at 1:15 AM, wrote:
> 2.7 should absolutely be able to support Tru64 (even though it currently
> may not - that would be a bug). Any potential contributor to fix Tru64
> support
> should find it "easy" to add fixes.
>
> So being cautious and following existing code sounds like
Zitat von Terry Reedy :
On 9/4/2012 9:00 AM, Andrew Svetlov wrote:
Aha, ./Doc/whatsnew/3.0.rst declares dropping support for Tru64.
Several files in repo mention it, though.
That suggests that it should be added to PEP11. Martin is the PEP
editor, so I guess it is his final decision.
I'd
Zitat von Trent Nelson :
OpenVMS is an interesting one though; it's still actively supported
by HP on Itanium. I've got an Itanium earmarked marked for OpenVMS
"for an even rainier day", but I wouldn't know OpenVMS is it smacked
me in the head, so, not a high priority at the mo
Zitat von Chris Jerdonek :
And for Python 2.7 when adding new tests
Hmm. Adding new tests to 2.7 is a questionable activity in the first
place - it should be done very carefully.
does this mean we should
write those tests in a way that attempts to have them pass on Tru64
(e.g. by following
Zitat von Andrew Svetlov :
http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_subprocess.py#l374
is link to comment,
http://bugs.python.org/issue1063571 — issue in bugtracker.
Is it still up to date? Bug has been created in 2004.
I don't see Tru64 in list of available buildbots.
Do
On 9/4/2012 9:00 AM, Andrew Svetlov wrote:
Aha, ./Doc/whatsnew/3.0.rst declares dropping support for Tru64.
Several files in repo mention it, though.
That suggests that it should be added to PEP11. Martin is the PEP
editor, so I guess it is his final decision.
--
Terry Jan Reedy
__
On 9/4/2012 5:24 AM, Andrew Svetlov wrote:
Unittests for subprocess module has weird comment:
We cannot use os.path.realpath to canonicalize the path, since it
doesn't expand Tru64 {memb} strings.
See bug 1063571.
http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_subprocess.py#l374
is
On Tue, Sep 04, 2012 at 02:24:10AM -0700, Andrew Svetlov wrote:
> Is it still up to date? Bug has been created in 2004.
> I don't see Tru64 in list of available buildbots.
>
> Do we need to care about this platform? And how to make sure what
> existing code works fine for that?
>
> Or maybe we can
On Tue, 04 Sep 2012 15:19:38 +0300, Andrew Svetlov
wrote:
> On Tue, Sep 4, 2012 at 3:11 PM, Antoine Pitrou wrote:
> > I don't think so. If some hypothetical Tru64 user cares, they can
> > probably open a bug on the tracker.
> >
> Thanks.
I used to work on Tru64 systems many years ago.
Accordin
Aha, ./Doc/whatsnew/3.0.rst declares dropping support for Tru64.
Several files in repo mention it, though.
On Tue, Sep 4, 2012 at 3:19 PM, Andrew Svetlov wrote:
> On Tue, Sep 4, 2012 at 3:11 PM, Antoine Pitrou wrote:
>> I don't think so. If some hypothetical Tru64 user cares, they can
>> probabl
On Tue, Sep 4, 2012 at 3:11 PM, Antoine Pitrou wrote:
> I don't think so. If some hypothetical Tru64 user cares, they can
> probably open a bug on the tracker.
>
Thanks.
--
Thanks,
Andrew Svetlov
___
Python-Dev mailing list
Python-Dev@python.org
http:/
On Tue, 4 Sep 2012 12:24:10 +0300
Andrew Svetlov wrote:
> Unittests for subprocess module has weird comment:
> We cannot use os.path.realpath to canonicalize the path, since it
> doesn't expand Tru64 {memb} strings.
> See bug 1063571.
> http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_
On Tue, Sep 4, 2012 at 5:02 AM, Victor Stinner wrote:
>> Or maybe we can drop support for Tru64 as well as we already does it
>> for, say, VMS?
>
> See the PEP 11 for unsupported platforms.
> http://www.python.org/dev/peps/pep-0011/#no-longer-supported-platforms
>
> "Name: VMS
> Unsupported in: Py
2012/9/4 Andrew Svetlov :
> I don't see Tru64 in list of available buildbots.
Nope, there is no Tru64 buildbot.
> Do we need to care about this platform? And how to make sure what
> existing code works fine for that?
I don't know this OS. According to Wikipedia, it's a closed source OS
which onl
On Tue, Sep 4, 2012 at 2:24 AM, Andrew Svetlov wrote:
> Unittests for subprocess module has weird comment:
> We cannot use os.path.realpath to canonicalize the path, since it
> doesn't expand Tru64 {memb} strings.
> See bug 1063571.
> http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_su
Unittests for subprocess module has weird comment:
We cannot use os.path.realpath to canonicalize the path, since it
doesn't expand Tru64 {memb} strings.
See bug 1063571.
http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_subprocess.py#l374
is link to comment,
http://bugs.python.org/issue
21 matches
Mail list logo
