[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Roundup Robot]

Roundup Robot  added the comment:

New changeset ca236138f0ce by Ned Deily in branch '2.7':
Issue #8746: Use tempfile module to get tempdir and randomize the
http://hg.python.org/cpython/rev/ca236138f0ce

New changeset 4e4554aa1453 by Ned Deily in branch '3.2':
Issue #8746: Use tempfile module to get tempdir and randomize the
http://hg.python.org/cpython/rev/4e4554aa1453

New changeset 080035e58bab by Ned Deily in branch 'default':
Issue #8746: Use tempfile module to get tempdir and randomize the
http://hg.python.org/cpython/rev/080035e58bab

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


--
nosy: +eric.araujo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Thanks for the additional tests, Garrett.  I've applied them (modulo a fix).  
I've also applied the corrections to configure which should make os.chflags() 
and os.lchflags() reappear again in BSD and OS X builds where supported.  I've 
also added and documented two new OS X specific file flags: UF_HIDDEN and 
UF_COMPRESSED. Applied in default (for 3.3), 3.2 (3.2.1), and 2.7 (2.7.3).

--
assignee: ronaldoussoren -> ned.deily
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> pending
type: compile error -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Roundup Robot]

Roundup Robot  added the comment:

New changeset abfe28e7e5cd by Ned Deily in branch '2.7':
Issue #8746: Correct faulty configure checks so that os.chflags() and
http://hg.python.org/cpython/rev/abfe28e7e5cd

New changeset 529e26aa4fa3 by Ned Deily in branch '3.2':
Issue #8746: Correct faulty configure checks so that os.chflags() and
http://hg.python.org/cpython/rev/529e26aa4fa3

New changeset 9da64c0bdc33 by Ned Deily in branch 'default':
Issue #8746: Correct faulty configure checks so that os.chflags() and
http://hg.python.org/cpython/rev/9da64c0bdc33

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

I apologize for taking so long with this. The attached patch is for test_posix 
against trunk (I shuffled around some code and extended some things to improve 
PosixTester.tearDown). Let me know if I need to wash, rinse, repeat for py3k, 
etc.

Thanks!

# Standard ports copy of python 2.7 without the *chflags configure fix.

$ python2.7 Lib/test/test_posix.py 
testNoArgFunctions (__main__.PosixTester) ... ok
test_access (__main__.PosixTester) ... ok
test_chdir (__main__.PosixTester) ... ok
test_chflags (__main__.PosixTester) ... skipped 'test needs os.chflags()'
test_chown (__main__.PosixTester) ... ok
test_confstr (__main__.PosixTester) ... ok
test_dup (__main__.PosixTester) ... ok
test_dup2 (__main__.PosixTester) ... ok
test_fchown (__main__.PosixTester) ... ok
test_fdopen (__main__.PosixTester) ... ok
test_fstat (__main__.PosixTester) ... ok
test_fstatvfs (__main__.PosixTester) ... ok
test_ftruncate (__main__.PosixTester) ... ok
test_getcwd_long_pathnames (__main__.PosixTester) ... ok
test_getresgid (__main__.PosixTester) ... ok
test_getresuid (__main__.PosixTester) ... ok
test_initgroups (__main__.PosixTester) ... ok
test_lchflags_regular_file (__main__.PosixTester) ... skipped 'test needs 
os.lchflags()'
test_lchflags_symlink (__main__.PosixTester) ... skipped 'test needs 
os.lchflags()'
test_lchown (__main__.PosixTester) ... ok
test_lsdir (__main__.PosixTester) ... ok
test_osexlock (__main__.PosixTester) ... ok
test_osshlock (__main__.PosixTester) ... ok
test_pipe (__main__.PosixTester) ... ok
test_setresgid (__main__.PosixTester) ... ok
test_setresgid_exception (__main__.PosixTester) ... ok
test_setresuid (__main__.PosixTester) ... ok
test_setresuid_exception (__main__.PosixTester) ... ok
test_stat (__main__.PosixTester) ... ok
test_statvfs (__main__.PosixTester) ... ok
test_strerror (__main__.PosixTester) ... ok
test_tempnam (__main__.PosixTester) ... ok
test_tmpfile (__main__.PosixTester) ... ok
test_umask (__main__.PosixTester) ... ok
test_utime (__main__.PosixTester) ... ok

--
Ran 35 tests in 0.020s

OK (skipped=3)

# Hand compiled version using sources from trunk.

$ /scratch/python/2.7/bin/python Lib/test/test_posix.py 
testNoArgFunctions (__main__.PosixTester) ... ok
test_access (__main__.PosixTester) ... ok
test_chdir (__main__.PosixTester) ... ok
test_chflags (__main__.PosixTester) ... ok
test_chown (__main__.PosixTester) ... ok
test_confstr (__main__.PosixTester) ... ok
test_dup (__main__.PosixTester) ... ok
test_dup2 (__main__.PosixTester) ... ok
test_fchown (__main__.PosixTester) ... ok
test_fdopen (__main__.PosixTester) ... ok
test_fstat (__main__.PosixTester) ... ok
test_fstatvfs (__main__.PosixTester) ... ok
test_ftruncate (__main__.PosixTester) ... ok
test_getcwd_long_pathnames (__main__.PosixTester) ... ok
test_getresgid (__main__.PosixTester) ... ok
test_getresuid (__main__.PosixTester) ... ok
test_initgroups (__main__.PosixTester) ... ok
test_lchflags_regular_file (__main__.PosixTester) ... ok
test_lchflags_symlink (__main__.PosixTester) ... ok
test_lchown (__main__.PosixTester) ... ok
test_lsdir (__main__.PosixTester) ... ok
test_osexlock (__main__.PosixTester) ... ok
test_osshlock (__main__.PosixTester) ... ok
test_pipe (__main__.PosixTester) ... ok
test_setresgid (__main__.PosixTester) ... ok
test_setresgid_exception (__main__.PosixTester) ... ok
test_stat (__main__.PosixTester) ... ok
test_statvfs (__main__.PosixTester) ... ok
test_strerror (__main__.PosixTester) ... ok
test_tempnam (__main__.PosixTester) ... ok
test_tmpfile (__main__.PosixTester) ... ok
test_umask (__main__.PosixTester) ... ok
test_utime (__main__.PosixTester) ... ok

--
Ran 35 tests in 0.009s

OK

--
Added file: http://bugs.python.org/file22337/issue8746-test_posix.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
versions: +Python 3.3 -Python 3.1

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Tests for the posix module should go in test_posix. The name 'posix' is used 
very loosely in python, it is basicly used as an alias for 'unixy'.

I'm not too happy about replicating the definition of the flags, as Ned noted 
the flags are also defined in Lib/stat.py.  I'd keep them out of posixmodule as 
the current definitions in Lib/stat.py should be valid on all platforms that 
currently support these flags.

W.r.t testing: there should be some simple smoke tests, basicly just enough to 
ensure that the function is available and that it links up to the right system 
call. There is no need to perform un exhaustive test of the system call, that 
should be done by the os vendor.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

On Mon, Jan 17, 2011 at 5:11 PM, Ned Deily  wrote:
>
> Ned Deily  added the comment:
>
> There is an existing test_lchflags in Lib/test/test_posix.py.  Additional 
> test cases should go there.

Ok, but again this isn't POSIX functionality -- it's a BSD functional piece.

Another thing that's nasty that I've discovered is that the
function prototype isn't the same across the board. After things are
consolidated in FreeBSD I'll talk to the NetBSD and OpenBSD folks.
Thanks!
-Garrett

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

There is an existing test_lchflags in Lib/test/test_posix.py.  Additional test 
cases should go there.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

Sorry -- got off-track for a while.

I assume these should go into Lib/test/test_os.py ?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Georg Brandl]

Changes by Georg Brandl :


--
priority: deferred blocker -> critical

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Ping - Garrett, any progress on updating the tests?  With dispatch, this could 
still make it into 3.2.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Georg Brandl]

Georg Brandl  added the comment:

Same for a4.

--
priority: release blocker -> deferred blocker

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Georg Brandl]

Changes by Georg Brandl :


--
priority: deferred blocker -> release blocker

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Georg Brandl]

Georg Brandl  added the comment:

This can be solved after 3.2a3.

--
assignee:  -> ronaldoussoren
nosy: +georg.brandl, ronaldoussoren
priority: release blocker -> deferred blocker

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

*NOUNLINK was not implemented by OSX, so there's actually a bug with the 
compile tests if you take that into consideration. And again, only FreeBSD 
defines *NOUNLINK. The other BSDs, not so much.

As far as the reason why I implemented the flags, the documentation that I was 
looking at didn't implement those flags. I looked at the latest documentation 
and it appears to be correct though. I will implement tests for *UNLINK and 
*HIDDEN (FWIW the tests I wrote are ok for cross-compilation because they just 
test for the existence of the values -- they don't test to ensure that the 
functionality is correct, like some of the logic in configure was recently 
`fixed' to do).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Nick: "lchflags". lchflags is only available in 10.5 or higher, unlike chflags 
which has been around for much longer.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Nick Dowell]

Nick Dowell  added the comment:

Why should it only be available on OS X if built with MACOSX_DEPLOYMENT_TARGET 
of 10.5 or higher?
chflags() should be available in earlier versions of the OS:
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/10.3/man2/chflags.2.html

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Actually the flags do already exist: note "(as defined in the stat module)" 
(http://docs.python.org/py3k/library/os.html#os.chflags).  Other than the new 
UF_HIDDEN, it looks like they are all hardwired there in Lib/stat.py.  There is 
something to be said for the approach in your patch in that it guarantees that 
the flags match the build OS definitions; the downside is some lack of 
portability and cross-testing.  Considering that there are other stat flags in 
there and have been for a long time, I'd be inclined to not change things other 
than throwing in UF_HIDDEN.

Regarding testing, perhaps the single most important thing would be to add a 
test that os.chflags is in fact present on systems where it is expected (to 
catch any future build problems like the one in this issue).  As you say, these 
are relatively transparent wrappers and we have to accept the OS's 
implementation.  Testing for the presence of os.lchflags is a bit trickier in 
that on OS X it should only be present if Python was built with a 
MACOSX_DEPLOYMENT_TARGET of 10.5 or higher.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

Do you prefer exhaustive tests, or just smoke tests? Honestly IMO, the OS 
should come prepackaged with tests to ensure that things function according to 
the requirements set forth in the manpage, so I would prefer the latter because 
the os methods in the posixmodule are nothing more than thin wrappers above the 
actual OS syscalls.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Changes by Garrett Cooper :


Added file: http://bugs.python.org/file18849/issue8746-py3k.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

I'll add new tests in the next submit for the bug, but here's the code to add 
the relevant symbols for common to *BSD and OSX, and the Snow Leopard+ and 
FreeBSD specific chflags of importance for python 2.7 and py3k.

--
Added file: http://bugs.python.org/file18848/issue8746-trunk.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Additional tests would be great.  It is probably reasonable to make some 
simplifying assumptions about which file systems the test directory would be 
run on.  I'm guessing other similar file system function tests are not 
bulletproof on all potential file system types on any modern OS.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Garrett Cooper]

Garrett Cooper  added the comment:

That definitely fixes detection for FreeBSD CURRENT with 2.7 and py3k for me.

I'm looking into providing some unit-tests, but the problem is that whether or 
not chflags functions on the underlying filesystem is problematic. For 
instance, it won't function on msdosfs (Linux calls it vfat), it won't function 
on ext[23] (AFAIK), and it didn't function on ZFS (until recently? I'm not sure 
whether or not the latest patches for ZFS enhance the filesystem to support 
this functionality). So unfortunately adding tests for this feature (while 
nice) would potentially be error prone.

Something I tried was:

>>> UF_IMMUTABLE = 2
>>> import tempfile
>>> f = tempfile.mkstemp()[1]
>>> os.getuid()
1000
>>> os.chflags('/tmp', UF_IMMUTABLE)
Traceback (most recent call last):
  File "", line 1, in 
OSError: [Errno 1] Operation not permitted: '/tmp'
>>> os.chflags(f, UF_IMMUTABLE)
>>> fd = open(f, 'w')
Traceback (most recent call last):
  File "", line 1, in 
IOError: [Errno 1] Operation not permitted: '/tmp/tmpi_hwY7'
>>> fd = open(f, 'r')
>>> fd = open(f, 'r')
>>> fd.read()
''
>>> os.chflags(f, 0)
>>> fd = open(f, 'w')
>>> fd.write('foo')
>>> fd.close()
>>> fd = open(f, 'r')
>>> fd.read()
'foo'
>>> fd.close()

Also, the flags are missing that are described in the manpage. I'll provide a 
patch for those.

Otherwise, it looks like everything's functioning as expected for basic 
end-to-end tests with chflags(2).

Thanks!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


Removed file: http://bugs.python.org/file18738/8746-2.6.6.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


Removed file: http://bugs.python.org/file18737/8746-2.7.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


Removed file: http://bugs.python.org/file18736/8746-3.1.2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


Added file: http://bugs.python.org/file18839/issue8746-27.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Changes by Ned Deily :


Added file: http://bugs.python.org/file18838/issue8746-31.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8746] os.chflags() and os.lchflags() are not built when they should be be

[Ned Deily]

Ned Deily  added the comment:

Thanks Garrett for reporting the problem and thank Nick for the patches.  It 
turns out the problem is more involved though the solution is similar. I've 
spent some time figuring out what went wrong here and documenting it in this 
issue so that no one else has to.  Ugh.

The relevant checkin events:

(1) (2009-07-16) r74038 changed the autoconf tests for chflags and lchflags to 
be m4a double-quoted (from '[' to '[[') to "ensure they don't get mangled".  
The test continues to use the AC_TRY_RUN macro and is working correctly.

(2) (2009-11-02) r76050 checked in a modified version of a patch from Gentoo to 
help support cross-compiling. The original patch was against a pre-r74038 
version; it wrapped the AC_TRY_RUN macro in an AC_CACHE_CHECK and a layer of 
quotes. In updating the patch for the then-current trunk (2.7), the 
significance of the r74038 change was apparently overlooked, resulting in an 
extra and faulty level of [...] quotes which end up in the configure test C 
source.  The test now gets compile errors on all Unix-y platforms but it is 
only significant on those that do support chflags and/or lchflags, i.e. BSD 
ones and OS X.

(3) (2010-01-30) The buggy test from trunk is merged into py3k (3.2) r77862, 
3.1 r77863, and 2.6 r77864.

(4) (2010-05-08) As part of Issue8510 updates to configure.in to work with 
autoconf 2.65, r80478 for py3k (3.2) and r80969 for trunk (2.7) converted the 
AC_TRY_RUN macro calls to ones using AC_RUN_IFELSE and AC_LANG_SOURCE. An extra 
level of quoting is added to preserve the existing, albeit buggy syntax.  The 
net effect is that the configure test C code generated is the same and still 
always fails with a compile error.

While I have not tested this on any BSD-like systems other than OS X, I believe 
this means that os.chflags and/or os.lchflags have been missing-in-action from 
builds on OSes where they should be supported for the following releases (i.e 
since 2009-11-02):

2.6.5
2.6.6
2.7
3.1.2
3.2a2

A side note for OS X: Apple first introduced lchflags() support in OS X 10.5.  
Since the python.org OS X installer pythons are traditionally built to an 
10.3/10.4 ABI, none of the OS X installers for the above Python releases would 
have had os.lchflags anyway (only os.chflags), except for the new 2.7 
32-bit/64-bit installer if the 2.7 test weren't otherwise broken.

The solution is to fix the buggy configure.in macros along the lines suggested 
by Nick.  I have created and tested three new patches to do this:

issue8746-py3k.patchfor py3k (3.2a2+)
issue8746-27.patch  for release-27-maint (2.7+)
issue8746-31.patch  for release-31-maint (3.1.2+)

A variant of the 3.1 patch should apply to release-26-maint (2.6.6+) however 
2.6 is now in security-fix-only mode.

In each case, the patch only modifies configure.in.  It is necessary to run 
autoreconf after applying and before checkin.  A simple test of the fix is to 
do ./configure before and after:

$ rm -f config.log config.status
$ ./configure
$ grep "expected identifier or '(' before " config.log
conftest.c:191: error: expected identifier or '(' before '[' token
conftest.c:200: error: expected identifier or '(' before ']' token
conftest.c:191: error: expected identifier or '(' before '[' token
conftest.c:200: error: expected identifier or '(' before ']' token
$ patch  release blocker
stage: unit test needed -> patch review
title: *chflags detection broken on FreeBSD 9-CURRENT -> os.chflags() and 
os.lchflags() are not built when they should be be
Added file: http://bugs.python.org/file18837/issue8746-py3k.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com