Hi Folks,
On Tue, Oct 15, 2013 at 8:28 PM, Jason Tishler wrote:
> Yaakov,
>
> On Wed, Oct 02, 2013 at 11:53:55PM -0500, Yaakov (Cygwin/X) wrote:
> > On 2013-08-15 12:50, Yaakov (Cygwin/X) wrote:
> > >On 2013-08-15 10:32, Corinna Vinschen wrote:
> > >>Jason? Is there any chance you could pick th
On 2013-08-15 12:50, Yaakov (Cygwin/X) wrote:
On 2013-08-15 10:32, Corinna Vinschen wrote:
Jason? Is there any chance you could pick this up?
I NMU'd both python and python3 for x86_64 earlier this week as a
prerequisite for the GNOME 3.8 update; so far they're both working well.
I just add
On Aug 15 13:48, Yaakov (Cygwin/X) wrote:
> On 2013-08-15 13:23, Corinna Vinschen wrote:
> >On Aug 15 12:50, Yaakov (Cygwin/X) wrote:
> >>I NMU'd both python and python3 for x86_64 earlier this week as a
> >>prerequisite for the GNOME 3.8 update; so far they're both working
> >>well.
> >
> >That so
On 2013-08-15 13:23, Corinna Vinschen wrote:
On Aug 15 12:50, Yaakov (Cygwin/X) wrote:
I NMU'd both python and python3 for x86_64 earlier this week as a
prerequisite for the GNOME 3.8 update; so far they're both working
well.
That sounds good, basically, but what means "NMU'd? :}
"Non-mainta
On Aug 15 12:50, Yaakov (Cygwin/X) wrote:
> On 2013-08-15 10:32, Corinna Vinschen wrote:
> >Jason? Is there any chance you could pick this up?
>
> I NMU'd both python and python3 for x86_64 earlier this week as a
> prerequisite for the GNOME 3.8 update; so far they're both working
> well.
That s
On 2013-08-15 10:32, Corinna Vinschen wrote:
Jason? Is there any chance you could pick this up?
I NMU'd both python and python3 for x86_64 earlier this week as a
prerequisite for the GNOME 3.8 update; so far they're both working well.
Yaakov
Jason? Is there any chance you could pick this up?
On Aug 9 00:38, Yaakov (Cygwin/X) wrote:
> On 2013-07-30 20:52, Yaakov (Cygwin/X) wrote:
> >I have patchsets ready for 2.7.5 (to fix the parsetuple issue) and 3.2.5
> >in Ports git; see 3.2-thread-cygwin64.patch for my proposed solution,
> >wh
On 2013-07-30 20:52, Yaakov (Cygwin/X) wrote:
I have patchsets ready for 2.7.5 (to fix the parsetuple issue) and 3.2.5
in Ports git; see 3.2-thread-cygwin64.patch for my proposed solution,
which would have to be rebased to a newer version and expanded to all
the other platform-specific implementa
On 2013-07-30 17:54, Yaakov (Cygwin/X) wrote:
On 2013-06-03 23:30, Yaakov (Cygwin/X) wrote:
Jason,
As part of the 64bit bootstrap process, I packaged python3, but had to
configure it --without-threads due to a runtime error.
I think I tracked down the source of the problem:
The PyThread TLS
On 2013-06-03 23:30, Yaakov (Cygwin/X) wrote:
Jason,
As part of the 64bit bootstrap process, I packaged python3, but had to
configure it --without-threads due to a runtime error.
I think I tracked down the source of the problem:
The PyThread TLS APIs, added in 3.2 via issue 9786 (namely,
PyT
On Jun 10 10:32, Corinna Vinschen wrote:
> Hi Jason,
>
> On Jun 7 19:07, Jason Tishler wrote:
> > Yaakov,
> >
> > On Mon, Jun 03, 2013 at 11:30:28PM -0500, Yaakov (Cygwin/X) wrote:
> > > As part of the 64bit bootstrap process, I packaged python3, but had
> > > to configure it --without-threads d
Hi Jason,
On Jun 7 19:07, Jason Tishler wrote:
> Yaakov,
>
> On Mon, Jun 03, 2013 at 11:30:28PM -0500, Yaakov (Cygwin/X) wrote:
> > As part of the 64bit bootstrap process, I packaged python3, but had
> > to configure it --without-threads due to a runtime error. However,
> > I am finding now tha
Yaakov,
On Mon, Jun 03, 2013 at 11:30:28PM -0500, Yaakov (Cygwin/X) wrote:
> As part of the 64bit bootstrap process, I packaged python3, but had
> to configure it --without-threads due to a runtime error. However,
> I am finding now that this is not a regularly used configuration;
> several major
13 matches
Mail list logo
