Hi Jorge,
This is the mailing list for the Python language development itself. It's
used for discussion of features and topics on the development of Python.
You can use other mailing lists for questions as:
python-h...@python.org --> ask for help to other people on the python
community
tu...@pytho
Hello.
This mailing list is to work on developing Python (adding new
features to Python itself and fixing bugs); if you're having problems
learning, understanding or using Python, please find another forum.
Probably python-list/comp.lang.python mailing list/news group is the
best place; there a
Hi,
I dowloaded the Python 2.7.13 and install it as root . it installed in
my directory:
/usr/src/Python-2.7.13
Then I typed:
python and I had:
Python 2.7.13 (default, Mar 14 2017, 09:30:46)
[GCC 4.9.2 20150212 (Red Hat 4.9.2-6)] on linux2
Type "help", "copyright", "credits" or "license"
I have Xcode installed and other large projects build just fine. I ran
“./configure && make” in the “Python-2.7.13” directory and “make” generated two
errors both referring to the same thing missing. The exact error messages are
copied and pasted below.
dyld: lazy symbol binding failed: Symbol
On Wed, 30 Nov 2016 22:58:01 -0800
Benjamin Peterson wrote:
> On Wed, Nov 30, 2016, at 10:19, Antoine Pitrou wrote:
> > On Tue, 29 Nov 2016 23:07:14 -0800
> > Benjamin Peterson wrote:
> > > Okay, now that we're heard from the other side, and I lacking a concrete
> > > reason to delay the relea
On Wed, Nov 30, 2016, at 10:19, Antoine Pitrou wrote:
> On Tue, 29 Nov 2016 23:07:14 -0800
> Benjamin Peterson wrote:
> > Okay, now that we're heard from the other side, and I lacking a concrete
> > reason to delay the release, I'm putting 2.7.13 back at the original
> > dates.
>
> Serhiy may b
On Tue, 29 Nov 2016 23:07:14 -0800
Benjamin Peterson wrote:
> Okay, now that we're heard from the other side, and I lacking a concrete
> reason to delay the release, I'm putting 2.7.13 back at the original
> dates.
Serhiy may be thinking about https://bugs.python.org/issue28427
Regards
Antoine.
last one at the
> > end of 2019, presumably)? I too would like to know the intended use of the
> > extra time.
> >
> > Top-posted from my Windows Phone
> >
> > -Original Message-
> > From: "Benjamin Peterson"
> > Sent: 11/29/20
Raymond Hettinger" ; "Serhiy Storchaka"
>
> Cc: "Python-Dev@Python. Org"
> Subject: Re: [Python-Dev] Python 2.7.13 release dates
>
> Okay, by popular demand, 2.7.13 now happens in January.
>
> I'm curious what people are planning to do to 2.7
On 28.11.2016 20:38, Larry Hastings wrote:
> On 11/28/2016 10:42 AM, Guido van Rossum wrote:
>> Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding
>> off putting a new version of typing.py on typeshed until that's out.)
>
> Not set in stone, but I have a rough plan. I wa
11/29/2016 0:04
To: "Raymond Hettinger" ; "Serhiy Storchaka"
Cc: "Python-Dev@Python. Org"
Subject: Re: [Python-Dev] Python 2.7.13 release dates
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with t
Okay, by popular demand, 2.7.13 now happens in January.
I'm curious what people are planning to do to 2.7 with the extra 5
weeks. The 2.7 branch is a place to put occasional conservative bug
fixes, which we aggregate and release every 6 months. It shouldn't
really need special attention or become
> On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka wrote:
>
> On 28.11.16 09:06, Benjamin Peterson wrote:
>> I've have just updated PEP 373 to say that Python 2.7.13 release
>> candidate 1 will be released on December 3. The final will follow two
>> weeks later on December 17. If there are delays
On 11/28/2016 10:42 AM, Guido van Rossum wrote:
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm
holding off putting a new version of typing.py on typeshed until
that's out.)
Not set in stone, but I have a rough plan. I want the dust to settle
around 3.6 first. So, have
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm
holding off putting a new version of typing.py on typeshed until that's
out.)
On Mon, Nov 28, 2016 at 10:36 AM, Serhiy Storchaka
wrote:
> On 28.11.16 09:06, Benjamin Peterson wrote:
>
>> I've have just updated PEP 373 to say th
On 28.11.16 09:06, Benjamin Peterson wrote:
I've have just updated PEP 373 to say that Python 2.7.13 release
candidate 1 will be released on December 3. The final will follow two
weeks later on December 17. If there are delays in the process, the
final will likely to pushed into January.
Could
I've have just updated PEP 373 to say that Python 2.7.13 release
candidate 1 will be released on December 3. The final will follow two
weeks later on December 17. If there are delays in the process, the
final will likely to pushed into January.
Servus,
Benjamin
17 matches
Mail list logo
