Re: [Python-Dev] Testing the tests by modifying the ordering of dict items.

2012-12-22 Thread Mark Shannon

On 21/12/12 07:05, csebasha wrote:

Hello Mark,

Did you raise bug for this?



No need now. The hash randomization, which was added a while ago,
will render the tests obsolete.

Cheers,
Mark.

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


[Python-Dev] hg.python.org down

2012-12-22 Thread Stefan Krah
Hi,

hg.python.org seems to be unreachable (tested from various IP addresses).



Stefan Krah


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


Re: [Python-Dev] hg.python.org down

2012-12-22 Thread Nick Coghlan
On Sun, Dec 23, 2012 at 12:14 AM, Stefan Krah  wrote:
> Hi,
>
> hg.python.org seems to be unreachable (tested from various IP addresses).

The docs build daemon started complaining on python-checkins about
2:10 pm UTC (on the 22nd), so about the same time you noticed the
issue.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] hg.python.org down

2012-12-22 Thread Chris Jerdonek
On Sat, Dec 22, 2012 at 6:58 AM, Nick Coghlan  wrote:
> On Sun, Dec 23, 2012 at 12:14 AM, Stefan Krah  wrote:
>> Hi,
>>
>> hg.python.org seems to be unreachable (tested from various IP addresses).
>
> The docs build daemon started complaining on python-checkins about
> 2:10 pm UTC (on the 22nd), so about the same time you noticed the
> issue.

For the record, it seems to be back up.  I don't know since when
precisely, but the last of the complaints on python-checkins seems to
have been about two hours ago.  (The complaints were happening every 5
minutes.)

--Chris
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] [Distutils, Python3] Incorrect shared library extension on linux

2012-12-22 Thread Sandro Mani

Hello,

First: I'm using Python3 as available in Fedora rawhide 
(python3-3.3.0-2.fc19.x86_64).


Attempting to build a project using python3/distutils, I noticed that 
find_library_file would not find any library at all. Some investigation 
showed that this was due to the fact that libraries were searched with 
the ".cpython-33m.so" extension. Even more investigation showed that the 
library extension was read being overridden by the one defined in the 
/usr/lib64/python3.3/config-3.3m/Makefile shipped by python3-libs. See 
below for the detailed analysis. The python-versioned extension 
obviously makes no sense for regular shared objects which are not python 
binary modules, so this is clearly wrong. As a workaround I commented 
sysconfig.py@customize_compiler::235 (compiler.shared_lib_extension = 
so_ext, see below), and things seem to work.


Is this a distribution bug or an upstream bug?

Thanks,
Sandro

Detailed analysis:

setup.py:
def _find_library_file(self, library):
return self.compiler.find_library_file(self.compiler.library_dirs, 
library)


---
In function 
/usr/lib64/python3.3/distutils/unixcompiler.py@find_library_file::266:

shared_f = self.library_filename(lib, lib_type='shared')

In function 
/usr/lib64/python3.3/distutils/ccompiler.py@library_filename::882:

ext = getattr(self, lib_type + "_lib_extension")

-> Where does shared_lib_extension get defined?
* At /usr/lib64/python3.3/distutils/ccompiler.py::66
shared_lib_extension = None   -> default for abstract class
* At /usr/lib64/python3.3/distutils/unixcompiler.py::77
shared_lib_extension = ".so"  -> this is the correct value
* In function 
/usr/lib64/python3.3/distutils/sysconfig.py@customize_compiler::235

by /usr/lib64/python3.3/distutils/sysconfig.py@customize_compiler::235
compiler.shared_lib_extension = so_ext
by /usr/lib64/python3.3/distutils/sysconfig.py@customize_compiler::194
(cc, cxx, opt, cflags, ccshared, ldshared, so_ext, ar, ar_flags) = \
get_config_vars('CC', 'CXX', 'OPT', 'CFLAGS',
'CCSHARED', 'LDSHARED', 'SO', 'AR', 'ARFLAGS'))
by /usr/lib64/python3.3/distutils/sysconfig.py@get_config_vars::530
526 global _config_vars
527 if _config_vars is None:
528 func = globals().get("_init_" + os.name)  # -> os.name = posix
529 if func:
530 func()  # -> _init_posix, populates _config_vars
by /usr/lib64/python3.3/distutils/sysconfig.py@_init_posix::439
435 g = {}
436 # load the installed Makefile:
437 try:
438 filename = get_makefile_filename()  # 
/usr/lib64/python3.3/config-3.3m/Makefile

439 parse_makefile(filename, g)
...
476 global _config_vars
477 _config_vars = g  # -> _config_vars["SO"] = ".cpython-33m.so"
by /usr/lib64/python3.3/config-3.3m/Makefile::122
SO= .cpython-33m.so

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


Re: [Python-Dev] [Python-checkins] Cron /home/docs/build-devguide

2012-12-22 Thread Barry Warsaw
On Dec 22, 2012, at 03:36 PM, Terry Reedy wrote:

>I always reject the requests as I don't believe these messages belong here. I
>even asked, some months ago, on pydev who was responsible for the robot that
>sends these but got no answer. Today, apparently, another list admin decided
>on the opposite response and gave r...@python.org blanket permission to flood
>this list with irrelavancy. It it not my responsibility and I have no idea
>how to fix it.
>
>While people with push priviliges are supposed to subscribe to this list, I
>know there is at least one who unsubscribed because of the volume. This will
>only encourage more to leave, so I hope someone can stop it.

Actually, I made d...@dinsdale.python.org an acceptable alias so these
messages won't just fill up the hold queue of the list.  It did get the
problem fixed, didn't it? ;)

I don't remember the previous conversation.  If folks really don't want those
messages hitting the checkins list, then errors should probably be sent to
some address that can do something about the problem when they occur.  Maybe
that's not d...@dinsdale.python.org, or maybe that alias should point
somewhere else (is that address ever used in the good path?).  I have no idea
where that address is used.

As for the noise issue, well, I hope such failures shouldn't happen very
often.  We can set up an auto-discard, but then I worry that problems will
just go unnoticed for days.

-Barry

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


Re: [Python-Dev] [Python-checkins] Cron /home/docs/build-devguide

2012-12-22 Thread M.-A. Lemburg


On 22.12.2012 21:36, Terry Reedy wrote:
> 
> On 12/22/2012 1:30 PM, Cron Daemon wrote:
>> abort: error: Connection timed out
>> ___
>> Python-checkins mailing list
>> python-check...@python.org
>> http://mail.python.org/mailman/listinfo/python-checkins
> 
> As a volunteer checkin-list admin, I occasionally get messages like this:
> '''
> As list administrator, your authorization is requested for the
> following mailing list posting:
> 
> List:python-check...@python.org
> From:r...@python.org
> Subject: Cron  /home/docs/build-devguide
> Reason:  Message has implicit destination
> 
> At your convenience, visit:
> 
> http://mail.python.org/mailman/admindb/python-checkins
> 
> to approve or deny the request.
> '''
> 
> I always reject the requests as I don't believe these messages belong here. I 
> even asked, some
> months ago, on pydev who was responsible for the robot that sends these but 
> got no answer. Today,
> apparently, another list admin decided on the opposite response and gave 
> r...@python.org blanket
> permission to flood this list with irrelavancy. It it not my responsibility 
> and I have no idea how
> to fix it.

You can add a sender filter to have the messages automatically discarded.

> While people with push priviliges are supposed to subscribe to this list, I 
> know there is at least
> one who unsubscribed because of the volume. This will only encourage more to 
> leave, so I hope
> someone can stop it.

I think such messages should go to a sys admin list.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Dec 22 2012)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...   http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/

2012-12-14: Released mxODBC.Connect 2.0.2 ... http://egenix.com/go38
2013-01-22: Python Meeting Duesseldorf ... 31 days to go

: Try our mxODBC.Connect Python Database Interface for free ! ::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Cron /home/docs/build-devguide

2012-12-22 Thread Terry Reedy

On 12/22/2012 3:46 PM, Barry Warsaw wrote:

On Dec 22, 2012, at 03:36 PM, Terry Reedy wrote:



Actually, I made d...@dinsdale.python.org an acceptable alias so these
messages won't just fill up the hold queue of the list.  It did get the
problem fixed, didn't it? ;)


It solved the admin problem for we two, but over 100(?) people, 
including me, got a slew of bogus checkin messages.



I don't remember the previous conversation.  If folks really don't want those
messages hitting the checkins list, then errors should probably be sent to
some address that can do something about the problem when they occur.  Maybe
that's not d...@dinsdale.python.org, or maybe that alias should point
somewhere else (is that address ever used in the good path?).  I have no idea
where that address is used.

As for the noise issue, well, I hope such failures shouldn't happen very
often.  We can set up an auto-discard, but then I worry that problems will
just go unnoticed for days.


They should be sent to the small group of people who can usefully 
respond to them.


--
Terry Jan Reedy

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