[Python-Dev] Re: Packing a long list of numbers into memory

[Facundo Batista]

El lun, 11 de oct. de 2021 a la(s) 06:50, Simon Cross
(hodgestar+python...@gmail.com) escribió:

> Multiprocessing sort of added support for this via multiprocessing.Array -- 
> see 
> https://stackoverflow.com/questions/9754034/can-i-create-a-shared-multiarray-or-lists-of-lists-object-in-python-for-multipro.
>  I haven't looked at what multiprocessing.Array does under the hood.
>
> Summary of the StackOverflow answer for those who don't feel like clicking:
>
>mp_arr = mp.Array(c.c_double, size)
># then in each new process create a new numpy array using:
>arr = np.frombuffer(mp_arr.get_obj())

Right, this is very close to what I had in mind for the "example with
numpy.array" that I want to code next (as I just said in the response
to Gregory, this is a series of implementations for pedagogical
purposes trying to teach parallel processing).

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/YTEO6B3TBD6PHWKRMP6F46P25HFN4ZU5/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Packing a long list of numbers into memory

[Facundo Batista]

El dom, 10 de oct. de 2021 a la(s) 15:20, Gregory P. Smith
(g...@krypto.org) escribió:

>> Is that because my particular case is very uncommon? Or maybe we *do*
>> want this but we don't have it yet? Or do we already have a better way
>> of doing this?
>>
>> Thanks!
>>
>> [0] https://linkode.org/#95ZZtVCIVtBbx72dURK7a4
>
>
> My first reaction on seeing things like this is "Why not use a numpy.array?"

Yes, there is a plan to use `numpy.array` in another example (I'm
trying to just use stdlib for pedagogical purposes).

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ZSFAE3JIOLJ7KITLAPG6FTHF4SQ63D3G/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Packing a long list of numbers into memory

[Facundo Batista]

El dom, 10 de oct. de 2021 a la(s) 11:50, Serhiy Storchaka
(storch...@gmail.com) escribió:
>
> 10.10.21 17:19, Facundo Batista пише:
> > I have a long list of nums (several millions), ended up doing the following:
> >
> > struct.pack_into(f'{len(nums)}Q', buf, 0, *nums)
>
> Why not use array('Q', nums)?

You mean `array` from the `array` module? The only way I see using it
is like the following:

>>> shm = shared_memory.SharedMemory(create=True, size=total_size)
>>> a = array.array('Q', nums)
>>> shm.buf[l_offset:r_offset] = a.tobytes()

But I don't like it because of the `tobytes` call, which will produce
a huge bytearray only to insert it in the shared memory buffer.

That's why I liked `pack_into`, because it will write directly into
the memory view.

Or I'm missing something?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/52NGDRMD3BR4ZTT3KGF6FNNGQIIPXBWY/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Packing a long list of numbers into memory

[Facundo Batista]

Hello everyone!

I need to pack a long list of numbers into shared memory, so I thought
about using `struct.pack_into`.

Its signature is

struct.pack_into(format, buffer, offset, v1, v2, ...)

I have a long list of nums (several millions), ended up doing the following:

struct.pack_into(f'{len(nums)}Q', buf, 0, *nums)

However, passing all nums as `*args` is very inefficient [0]. So I
started wondering why we don't have something like:

struct.pack_into(format, buffer, offset, values=values)

which would receive the list of values directly.

Is that because my particular case is very uncommon? Or maybe we *do*
want this but we don't have it yet? Or do we already have a better way
of doing this?

Thanks!

[0] https://linkode.org/#95ZZtVCIVtBbx72dURK7a4

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/4WYEIBOXPQPQ5EQL5WRYI6X7W36I6UQJ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Buildbot migrated to a new server

[Facundo Batista]

Thanks Victor and the rest of the Night’s Watch for all the work in
our buildbots!

El jue., 3 de sep. de 2020 a la(s) 12:08, Victor Stinner
(vstin...@python.org) escribió:
>
> Hi,
>
> tl; dr Buildbots were unstable for 3 weeks but the issue is mostly resolved.
>
>
> Since last January, the disk of the buildbot server was full every 2
> weeks and The Night’s Watch had to fix it in the darkness for you
> (usually, remove JUnit files and restart the server). The old machine
> only has 8 GB for the whole system and all data, whereas buildbot
> workers produce large JUnit (XML) files (around 5 MB per file).
>
> Three weeks ago, Ernest W. Durbin III provided us a new machine with a
> larger disk (60 GB) and installed PostgreSQL database (whereas SQLite
> was used previously). He automated the installation of the machine,
> but also (great new feature!) automated reloading the Buildbot server
> when a new configuration is pushed in the Git repository. The
> configuration is public and maintained at:
> https://github.com/python/buildmaster-config/
>
> The migration was really smooth, except that last week, we noticed
> that workers started to be disconnected every minute, and then filled
> their temporary directory with temporary compiler files leaked by
> interrupted builds. Buildbot owners have to update their client
> configuration and remove manually temporary files:
> https://mail.python.org/archives/list/python-buildb...@python.org/thread/SZR2OLH67OYXSSADSM65HJYOIMFF44JZ/
>
> Most buildbot worker configurations have been updated and the issue is
> mostly resolved.
>
> There is another minor issue, HTTPS connections also closed after 1
> minute and so the web page is refreshed automatically every minute.
> The load balancer configuration should be adjusted:
> https://bugs.python.org/issue41701
>
> Victor
> --
> Night gathers, and now my watch begins. It shall not end until my death.
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-dev@python.org/message/DYUX5EEDAX3IO66QOICPK3VNEENSEIIQ/
> Code of Conduct: http://python.org/psf/codeofconduct/



-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ZQRFBESKBCNOMFYZNJWSERUB477ZPYLW/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PR stuck in Travis

[Facundo Batista]

El vie., 21 de ago. de 2020 a la(s) 15:54, Guido van Rossum
(gu...@python.org) escribió:
>
> Does closing and reopening the PR work?
>

Yeap, it worked, thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/7WLH24JDFEYZ6DN77Z2QKTQOQ7P2KEFR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] PR stuck in Travis

[Facundo Batista]

Hello!

I want to land this PR:

  https://github.com/python/cpython/pull/21466

It's doc only, so it only run the docs part in GH actions. All fine,
except Travis, which is "required", but didn't finish. I'm not finding
a way to restart that job.

- from Github: I don't find any restart/resend job or similar (and in
the line corresponding to Travis in the checks list, I don't have a
"details").

- from Travis: I can not make that PR to appear in
https://travis-ci.com/github/python/cpython/pull_requests , even if I
click on "show me more" a lot (a *lot*). I don't know if there's a
specific way to show the job "by PR", and not "by build" (which I
don't know).

- from git: I could tell the author to push an empty commit, that
probably would do it, but I'd consider this a last resource.

Did you suffer from this before? Which is the recommended course of action?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/2PXBKFHOAWLFVDX2HSAPUFJGAPI32LO4/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Procedure for trivial PRs

[Facundo Batista]

El jue., 13 de ago. de 2020 a la(s) 18:42, Terry Reedy
(tjre...@udel.edu) escribió:

> The backport bot occasionally fails, sometimes for external reasons.  If
> you hit a problem, you can ask me for help as I have probably hit all
> the failure modes by now.

Thanks! One of the backport failed so I (per the bot's suggestion)
learned and used the cherry-picker tool.

But while doing that Victor kicked the bot a little, and that time it
worked ok...

Thanks for the help, everybody!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/PKMUZUNKQJUZCIRRJLSWZBCR7LV5YXGQ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Procedure for trivial PRs

[Facundo Batista]

El jue., 13 de ago. de 2020 a la(s) 17:41, Facundo Batista
(facundobati...@gmail.com) escribió:
>
> El jue., 13 de ago. de 2020 a la(s) 17:32, Facundo Batista
> (facundobati...@gmail.com) escribió:
>
> > >>
> > >
> > > As a core dev you can still merge it yourself without needing to wait for 
> > > review, even when it has the "awaiting core review" label.
> >
> > Awesome, thanks for the help.
>
> I'll create two new PRs, for 3.8 and 3.9, and when landed remove the
> "need backport tags" you added... a couple of questions, though:
>
> a) is it ok to touch 3.9, as it's in rc1?
>
> b) shall I create two brand new branches for those PRs, or there's
> some way in github/git to "just propose this same change to the other
> branches"?
>
> Thanks!
>
> (sorry for the simplicity of the questions, but it was a long time
> since I touched Python core, and infrastructure changed so much!)

Jaja, the bots came to my rescue! There I backported the changes.

I love all that automation, thanks for workin on that.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/334XJRLUFON5LHG6U3IS5OHB6JUCGJEU/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Procedure for trivial PRs

[Facundo Batista]

El jue., 13 de ago. de 2020 a la(s) 17:32, Facundo Batista
(facundobati...@gmail.com) escribió:

> >>
> >
> > As a core dev you can still merge it yourself without needing to wait for 
> > review, even when it has the "awaiting core review" label.
>
> Awesome, thanks for the help.

I'll create two new PRs, for 3.8 and 3.9, and when landed remove the
"need backport tags" you added... a couple of questions, though:

a) is it ok to touch 3.9, as it's in rc1?

b) shall I create two brand new branches for those PRs, or there's
some way in github/git to "just propose this same change to the other
branches"?

Thanks!

(sorry for the simplicity of the questions, but it was a long time
since I touched Python core, and infrastructure changed so much!)

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/W5EVJKLWKJ5EAYAUSRAGOR5GOSJDD7WD/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Procedure for trivial PRs

[Facundo Batista]

El jue., 13 de ago. de 2020 a la(s) 16:55, Mariatta
(maria...@python.org) escribió:
>
>
> On Thu, Aug 13, 2020 at 12:51 PM Facundo Batista  
> wrote:
>>
>> It's waiting for a "core review", which is a good thing (and by all
>> means welcomed). But as we're saturated of PRs, the fix is small, and
>> I'm a core developer myself... shall I wait for a review from another
>> core developer, or should I just land it?
>>
>
> As a core dev you can still merge it yourself without needing to wait for 
> review, even when it has the "awaiting core review" label.

Awesome, thanks for the help.

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/N2BZYSEQSKFO7346CXYNUXQPSEYEGNWB/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Procedure for trivial PRs

[Facundo Batista]

Hello!

I just proposed a PR with a small fix to the docs. I'd like to know
the procedure to land it.

  https://github.com/python/cpython/pull/21851

It's super small, so no bug is opened for it, and IMO no mention is
needed in the NEWS for the fix.

It's waiting for a "core review", which is a good thing (and by all
means welcomed). But as we're saturated of PRs, the fix is small, and
I'm a core developer myself... shall I wait for a review from another
core developer, or should I just land it?

Thanks!!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/6HLUSOLE4DCXUWCWJ6JYAEEPJ52BGX24/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: About "python-porting" mail list

[Facundo Batista]

El mar., 14 de ene. de 2020 a la(s) 16:36, Mark Sapiro
(m...@msapiro.net) escribió:
>
> The list has been removed. The archives are still available at
> .
>

Thank you!!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ZIG6UGPU62P7AZ6RKIZLEBXYWQJU7RSX/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: About "python-porting" mail list

[Facundo Batista]

El dom., 23 de dic. de 2018 a la(s) 14:20, Barry Warsaw
(ba...@python.org) escribió:
>
> On Dec 23, 2018, at 07:29, Facundo Batista  wrote:
> >
> > This list (which I co-admin, with Georg) is getting less and less
> > traffic as months pass by. See:
> >
> >  https://mail.python.org/pipermail/python-porting/
> >
> > The interwebs has been collecting ton of resources about porting py2
> > to 3 during these years. Any not-yet-answered question surely can be
> > done in a list with more participants.
> >
> > Can we kill this list?
>
> Is it a maintenance burden?  If not, then maybe we should wait until 2.7 is 
> EOL’d?  There might be an uptick in traffic as reality sets in for more 
> people.

Hello! Happy new year!

Can we kill this list now? It's barely used, almost no send mails and
no replies...

Thanks,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/MCXHNUQAYIMIXHKISE46PVZA27WCPWGC/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: 3.10 or 4.0?

[Facundo Batista]

El jue., 28 de nov. de 2019 a la(s) 12:35, Facundo Batista
(facundobati...@gmail.com) escribió:

> Did we take a decision of what comes after 3.9?
>
> Do we have a PEP for that decision? (couldn't find it)

Thanks everybody for the responses.

So 3.10 it is, not a hard made decision, but the collective trend.

Should we have a PEP for this?

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/JXCEWN6MI7OMUAMCRJEKNSDPXTAKGBIL/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] 3.10 or 4.0?

[Facundo Batista]

Hello!

Did we take a decision of what comes after 3.9?

Do we have a PEP for that decision? (couldn't find it)

(not arguing in favor of one or another, just want to know the
rationale behind it)

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/M5N3PZP4IUMKRZJKKJQA4IXK5VDX5MOP/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: What to do about invalid escape sequences

[Facundo Batista]

El lun., 5 de ago. de 2019 a la(s) 01:25,
 escribió:
>
> We should revisit what we want to do (if anything) about invalid escape 
> sequences.
>
> For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning which 
> is visible by default.  The intention is to make it a SyntaxError in Python 
> 3.9.

What about allowing in 3.8 to from __future__ import this
SyntaxWarning (so anybody can start kicking own code's tires), then
3.9 could make it a real SyntaxWarning, and 4.0 (3.10?) make it a
SyntaxError?

Of course, in a year or so we could decide to delay the last two steps
even more...

Regards,


--
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/S62JZC6TSJHBGX4IDWF7XATDQ6HV2YVH/

Re: [Python-Dev] About "python-porting" mail list

[Facundo Batista]

El dom., 23 de dic. de 2018 a la(s) 14:20, Barry Warsaw
(ba...@python.org) escribió:

> > Can we kill this list?
>
> Is it a maintenance burden?  If not, then maybe we should wait until 2.7 is 
> EOL’d?  There might be an uptick in traffic as reality sets in for more 
> people.
>

It's a good idea to wait until next year.

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] About "python-porting" mail list

[Facundo Batista]

Hello!

This list (which I co-admin, with Georg) is getting less and less
traffic as months pass by. See:

  https://mail.python.org/pipermail/python-porting/

The interwebs has been collecting ton of resources about porting py2
to 3 during these years. Any not-yet-answered question surely can be
done in a list with more participants.

Can we kill this list?

Thanks! Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Servicing pypi.python.org

[Facundo Batista]

El jue., 18 de oct. de 2018 a la(s) 00:07, Donald Stufft
(don...@stufft.io) escribió:

> tl;dr: can we have a (semi)permanent redirect from pypi.python.org to 
> pypi.org?
>
>
>
> This already exists:

Indeed, it works! I was in a place with a very crappy internet, but I
never suspected the issue I was getting was part of that.

Anyway, everything is fine! Thanks for the help and sorry for the noise :)

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Servicing pypi.python.org

[Facundo Batista]

Hola!

tl;dr: can we have a (semi)permanent redirect from pypi.python.org to pypi.org?

I own/maintain a project called `fades`, which is an automatic
virtualenv creator/manager [0].

While it relies on `pip` itself for the heavy work on the virtualenv
itself, `fades` checks if all required dependencies can be served [1]
*before* starting to do the rest of the work, which saves a lot of
time.

I just noticed that this is broken, because `pypi.python.org` is dead,
and the service should be queried under `pypi.org` directly.

We probably should have switched to the new domain months ago, but you
know how it's open source, it frequently happens that one has to live
first and that leaves no time for fun work.

So, can we have a (semi)permanent redirect from pypi.python.org to pypi.org?

This will help `fades` directly (even if we fix this and release soon,
there will be a lot of older fades in the wild hitting the de[recated
URL) and probably other projects using the old URL.

I suspect that having a generic redirect will not be burdensome server side.

Can we? Can we? P-p-please??? :)

Thanks in advance.

[0] fades.readthedocs.io
[1] using URLs like `https://pypi.python.org/pypi/Twisted/json`

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Process to remove a Python feature

[Facundo Batista]

2018-05-02 14:24 GMT-03:00 Brett Cannon :

>> Maybe we should create a tool to list features scheduled for removal,
>> and open a discussion to check each removal?
>
> I don't know if a tool is necessary. We could have a meta issue or text file
> somewhere to track what's to be removed in a certain version.

Maybe a specific PEP that list all removals that happened, those that
will happen next version, and next ones after that?

IOW, a single point where one can see which features/details will fly
away and when.

Probably it's a good idea to see everything at once and evaluate if
"we're removing too many things at once", and have a better
deprecation/removal cadence.

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Impact of Namedtuple on startup time

[Facundo Batista]

On Mon, Jul 17, 2017 at 9:43 AM, Antoine Pitrou  wrote:

> As for 2), startup time is actually a very important consideration
> nowadays, both for small scripts *and* for interactive use with the
> now very wide-spread use of Jupyter Notebooks.  A 1 ms. cost when
> importing a single module can translate into a large slowdown when your
> library imports (directly or indirectly) hundreds of modules, many of
> which may create their own namedtuple classes.

My experience inside Canonical is that golang stole a lot of "codebase
share" from Python, and (others and mine) talks hit two walls, mainly:
one is memory consumption, and the other is startup time.

So yes, startup time is important for user-faced scripts and services.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Translated Python documentation

[Facundo Batista]

On Wed, Feb 22, 2017 at 3:04 PM, Serhiy Storchaka  wrote:

> My largest apprehension is that the documentation can be outdated and
> quickly become degraded if main contributors left it.

This is why we focus in the Tutorial only, but also:

a) The tutorial is mostly the "entry point" to Python's doc, so being
it in Spanish for Spanish speakers lowers the barrier a lot

b) At some point you need to understand English docs, so translating
the library reference should not be that important

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Translated Python documentation

[Facundo Batista]

On Wed, Feb 22, 2017 at 9:10 AM, Victor Stinner
 wrote:

> There are a least 3 groups of people who are translating the Python
> documentation in their mother language (french, japanese, spanish).

We translated (and even printed/published) the Tutorial (we're
currently maintaining the Py2 and Py3 branches).

But only the tutorial, that is a smaller and steadier doc.


> For me, the most impotant point would be to give access to the
> translated documentation from docs.python.org. For example, have a
> dropdown list with available languages.

To clarify: you're proposing to *serve* the translated files from
d.p.o? Or just a link to where those are served now?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Why does PEP 7/8 explicitly suggest 2 spaces after a period?

[Facundo Batista]

On Fri, May 20, 2016 at 1:27 PM, Brett Cannon  wrote:

> Is there a specific reason for calling out two spaces in comments after a
> period(I realize it's probably for consistency, but I sure don't ever think
> about this when I write comment)? Otherwise who actually still writes using
> two spaces after punctuation? :)

I couldn't find it in the reference but AFAIK is something that is
also done in ReStructured Text.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Problemas con modulos

[Facundo Batista]

2016-04-29 13:52 GMT-03:00 Guido van Rossum :

>  Thank you Facundo, and thanks for following up here! (I wonder if it
> wouldn't have been just as efficient if you had just BCC'ed the list to your
> original response? Or perhaps with a brief English note at the top?)

Probably yes, I didn't want to mess the list with non-english stuff :)

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Problemas con modulos

[Facundo Batista]

Just to mention that I already answered this (in Spanish, in private),
redirecting to proper lists.

Regards,

2016-04-29 5:04 GMT-03:00 Felipe Ruiz via Python-Dev :
>   Hola,
>
> Estoy intentando conectarme a twitter para recibir tweets, sin embargo
> algunos códigos que he bajado de internet, me indican que debo de instalar
> tweepy y matplotlib, lo hago y sigo recibiendo el mensaje de que no están
> instalados. tweepy no reporta problemas, lo invoco en la línea de comandos,
> todo bien, Igual con matplotlib requiere de varias dependencias (dateutils,
> numpy, tornado, etc, ya las instales) antes de su instalación, pero ya en el
> editor de Python, al ejecutar el código, me aparece el siguiente mensaje:
>
> ImportError: No module named 'matplotlib'
>
> alguna idea?
>
> Felipe
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/facundobatista%40gmail.com
>



-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Counting references to Py_None

[Facundo Batista]

Hello!

I'm seeing that our code increases the reference counting to Py_None,
and I find this a little strange: isn't Py_None eternal and will never
die?

What's the point of counting its references?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Web redirect to PyAr

[Facundo Batista]

On Mon, Mar 7, 2016 at 4:08 PM, Berker Peksağ  wrote:

>> At some point in the past we had a redirect from python.org/ar (note
>> the slash, not a point) to a PyAr site.
>>
>> Now it's not working, it 404s.
>>
>> It should be redirected to python.org.ar (note the point).
>
> Can you try again? It should be redirected to python.org.ar now.

Wonderful, it works! Thanks Berker!!

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Web redirect to PyAr

[Facundo Batista]

Hello!

Sending mail here because I really don't know where this is handled :)

At some point in the past we had a redirect from python.org/ar (note
the slash, not a point) to a PyAr site.

Now it's not working, it 404s.

It should be redirected to python.org.ar (note the point).

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 257 and __init__

[Facundo Batista]

On Mon, Jan 4, 2016 at 4:49 AM, Nick Coghlan  wrote:

> When some of the default settings for the pep8 utility became a
> problem, I was able to talk to the developers and persuade them to
> tune their defaults to be more in line with the actual PEP text, and
> keep their extensions to optional settings.

In that spirit, I opened an issue [0] in the pep257 project to be able
to configure that and bypass the default behaviour, so the tool can be
used in a wider set of projects.

Thanks everybody for all the info.

Regards,

[0] https://github.com/GreenSteam/pep257/issues/171

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] PEP 257 and __init__

[Facundo Batista]

Hola!

(I was doubting in sending this mail to this list or to the normal
one, but as it affects a "style recommendation" we propose for the
whole community, I finally sent it here)

I was reading PEP 257 and it says that all public methods from a class
(including __init__) should have a docstring.

Why __init__?

It's behaviour is well defined (inits the instance), and the
initialization parameters should be described in the class' docstring
itself, right?

Or I am missing something?

Should we remove "__init__" (the class method, *not* the package file)
as to require docstrings in the PEP?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 257 and __init__

[Facundo Batista]

On Tue, Dec 29, 2015 at 4:38 PM, Andrew Barnert  wrote:

> Isn't the same thing true for every special method? There are lots of classes 
> where __add___ just says "a.__add__(b) = a + b" or (better following the PEP) 
> "Return self + value." But, in the rare case where the semantics of "a + b" 
> are a little tricky (think of "a / b" for pathlib.Path), where else could you 
> put it but __add__?
>
> Similarly, for most classes, there's only one of __init__ or __new__, and the 
> construction/initialization semantics are simple enough to describe in one 
> line of the class docstring--but when things are more complicated and need to 
> be documented, where else would you put it?

Yeap. Note that I'm ok to include a docstring when the actual
behaviour would deviate from the expected one as per Reference Docs.
My point is to not make it mandatory.


> I usually just don't bother. You can violate PEP 257 when it makes sense, 
> just like PEP 8. They're just guidelines, not iron-clad rules.

Yeap, but pep257 (the tool [0]) complains for __init__, and wanted to
know how serious was it.


[0] https://pypi.python.org/pypi/pep257

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Committing into which branches?

[Facundo Batista]

On Wed, Apr 22, 2015 at 6:46 PM, Brett Cannon br...@python.org wrote:

 The default branch is going to become 3.5, so you're fine.

Thanks!!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Committing into which branches?

[Facundo Batista]

Hola!

I just commited a simple improvement to HTTPError repr, and checking
in the source code page [0], I see that my commit has a small
default besides it; and other commits don't have that, but have 2.7,
or 3.4, etc...

So, question: Did I commit in the correct branch? Should I have done
anything different?

Thanks!

[0] https://hg.python.org/cpython/

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Not being able to compile: make: *** [Programs/_freeze_importlib] Error 1

[Facundo Batista]

Hello!

It's been a while since I compiled python and run the test suite.

Now that I'm starting to work in a patch, wanted to do that as a
sanity check, and even ./configure finishing ok, make fails :/
(I'm on Ubuntu Trusty, all packages updated, all dependencies
theorically installed).

Full trace here:

  http://linkode.org/TgkzZw90JUaoodvYzU7zX6

Before going into a deep debug, I thought about sending a mail to see
if anybode else hit this issue, if it's a common problem, if there's a
known workaround.

Thanks!!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] How to behave regarding commiting

[Facundo Batista]

Hola!

I'm asking this because quite some time passed since I was active in
the development of our beloved language.

I'm trying to not break any new rule not known by me.

I opened a bug recently [0], somebody else proposed a patch that I
like. However, that patch has no test. I will do a test for that code,
but then what?

Shall I just commit and push? Or the whole branch should be proposed
for further reviewing?

Thank you!!

[0] http://bugs.python.org/issue23887

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Not being able to compile: make: *** [Programs/_freeze_importlib] Error 1

[Facundo Batista]

On Thu, Apr 16, 2015 at 6:34 PM, R. David Murray rdmur...@bitdance.com wrote:

 Most likely you just need to run 'make touch' so that it doesn't try
 to rebuild stuff it doesn't need to (because we check in those
 particular build artifacts, like the frozen importlib).

make touch didn't fix it, but when doing that I noticed this message:

  Modules/Setup.dist is newer than Modules/Setup;
  check to make sure you have all the updates you
  need in your Modules/Setup file.
  Usually, copying Modules/Setup.dist to Modules/Setup will work.

I copied that file, and then make touch, and then the make finished OK!!!

Should we update the developer guide with these instructions, or all
this is unlikely to happen?

Thanks!!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] str.lstrip bug?

[Facundo Batista]

On Tue, Mar 10, 2015 at 2:27 PM, lou xiao lox.x...@gmail.com wrote:

 tiny➜ ~ python
 Python 2.7.5+ (default, Feb 27 2014, 19:37:08)
 [GCC 4.8.1] on linux2
 Type help, copyright, credits or license for more information.
 a='device_info'
 a.lstrip('device')
 '_info'
 a.lstrip('device_')
 'nfo'

On one hand, this is the development of python itself list; this
issue was more aimed to the general python list, of you was sure that
this is a real bug, to the issue tracker.

On the other hand, this is not a bug! If you pass a parameter to
lstrip it will (quoted from its help) remove characters in chars
instead., so the moment you pass device_, it removes all those
characers from the left... note that the 'i' is removed twice.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Enum is really serializable using json?

[Facundo Batista]

We have this issue closed as resolved:

  http://bugs.python.org/issue18264

It's called enum.IntEnum is not compatible with JSON serialisation,
and it looks that after a long conversation they added proper support
for it in Py3.4.

However, this is still failing:

Python 3.4.2 (default, Oct  8 2014, 13:18:07)
[GCC 4.9.1] on linux
 import enum, json
 Foo = enum.Enum('Foo', 'bar baz')
 json.dumps(Foo.bar)
Traceback (most recent call last):
...
TypeError: Foo.bar: 1 is not JSON serializable

Am I failing to understand the bug tracker saying the patch was
applied for Py3.4?

(thought it was more polite to ask here than to reopen the whole
thread in the issue tracker)

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Enum is really serializable using json?

[Facundo Batista]

On Sat, Feb 21, 2015 at 3:50 PM, Benjamin Peterson benja...@python.org wrote:

 Am I failing to understand the bug tracker saying the patch was
 applied for Py3.4?

 As the issue title suggests, IntEnum but not Enum supports JSON
 serialization.

Arghhh.. stupid of me. Sorry for the noise, and thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Redirection of ar.pycon.org

[Facundo Batista]

Hi!

Don't remember where to ask for changing the redirection of that
domain name. Somebody knows?

I need for the redirection to be to pycon.python.org.ar (and we'll
take care of proper year-by-year redirection from there).

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Add transform() and untranform() methods

[Facundo Batista]

On Thu, Nov 14, 2013 at 7:32 PM, Victor Stinner
victor.stin...@gmail.com wrote:

 I would prefer to split the registry of codecs to have 3 registries:

 - encoding (a better name can found): encode str=bytes, decode bytes=str
 - bytes: encode bytes=bytes, decode bytes=bytes
 - str:  encode str=str, decode str=str

 And add transform() and untransform() methods to bytes and str types.
 In practice, it might be same codecs registry for all codecs just with
 a new attribute.

I like this idea very much.

But to see IIUC, let me be more explicit... you'll have (of course,
always py3k-speaking):

- bytes.decode() - str ... here you can only use unicode encodings
- no bytes.encode(), like today
- bytes.transform() - bytes ... here you can only use things like
zlib, rot13, etc

- str.encode() - bytes ... here you can only use unicode encodings
- no str.decode(), like today
- str.transform() - str ... here you can only use things like... like what?

When to use decode/encode was always a major pain point for people, so
doing this extra separation and cleaning would bring more clarity to
when to use what.

Thanks!

--
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] The pysandbox project is broken

[Facundo Batista]

On Wed, Nov 13, 2013 at 4:37 AM, Maciej Fijalkowski fij...@gmail.com wrote:

 Do you think it would be productive to create an independent Python
 compiler, designed with sandboxing in mind from the beginning?

 PyPy sandbox does work FYI

 It might not do exactly what you want, but it both provides a full
 python and security.

If we have sandboxing using PyPy... what also we need to put Python
running in the browser? (like javascript, you know)

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Making submodules available when importing top one

[Facundo Batista]

(all this using Python 3.4.0a3+)

In the stdlib, I see that (as an example):

 import os
 os.path.abspath
function abspath at 0xb7123734
 os.path
module 'posixpath' from '/.../python/trunk/Lib/posixpath.py'


However, for other (newer) modules:

 import urllib
 urllib.requests.urlopen
Traceback (most recent call last):
  File stdin, line 1, in module
AttributeError: 'module' object has no attribute 'requests'
 import concurrent
 concurrent.futures
Traceback (most recent call last):
  File stdin, line 1, in module
AttributeError: 'module' object has no attribute 'futures'


So, is there a reason to not expose the submodules in the top module?
This should be fixed?

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] PEP 8 misnaming

[Facundo Batista]

Hello!

In the Maximum Line Length section of PEP 8 it says:

The preferred place to break around a binary operator is *after*
the operator, not before it.

And after that is an example (trimmed here):

if (width == 0 and height == 0 and
color == 'red' and emphasis == 'strong' or
highlight  100):
raise ValueError(sorry, you lose)

In the example the line is broken after the 'and' or 'or' *keywords*,
not after the '==' *operator* (which is the nice way of doing it).

Maybe the sentence above is misleading?

Thanks!

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Strange message error in socket.sendto() exception

[Facundo Batista]

Python 3.2 (r32:88445, Mar 25 2011, 19:28:28)
[GCC 4.5.2] on linux2
 import socket
 s = socket.socket()
 print(s.sendto.__doc__)
sendto(data[, flags], address) - count
...
 s.sendto(b'data', ('localhost', 3))
Traceback (most recent call last):
  File stdin, line 1, in module
socket.error: [Errno 32] Broken pipe

This is ok, I expected this. However, note what happens if I send unicode:

 s.sendto('data', ('localhost', 3))
Traceback (most recent call last):
  File stdin, line 1, in module
TypeError: sendto() takes exactly 3 arguments (2 given)

An error regarding the argument quantity? what?

Furthermore, where this message comes from? I tried to find, but the
only hint I get is that it could come from
./Modules/_ctypes/_ctypes.c... are we using ctypes to access socket
methods? it's strange, because sendto is defined in socketmodule.c.

Ideas? Thanks!

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Decisions about workflow

[Facundo Batista]

I know there's a big ideas exchange in this list about how to use
Mercurial in the Python project.

I know that still there is not wide and firm consensus about the whole
workflow to follow.

But maybe some small decisions are already taken, some suggestions
about the best way to do this or that, even if there are others that
are not taken.

Is this being documented somewhere?

Thank you!

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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: inter-branch workflow

[Facundo Batista]

On Wed, Mar 16, 2011 at 7:00 PM, Raymond Hettinger
raymond.hettin...@gmail.com wrote:

 I don't think the more complex workflow if worth it.  Mercurial is very user 
 friendly right out of the box will simple commands.  But as soon as you 
 require the branches to be inter-linked, you've made it much more difficult 
 to get simple checkins done.

+1 to keep it as simple as possible, at least until we get more time
using it and know better which added complexity pays off.

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] [Preview] Comments and change proposals on documentation

[Facundo Batista]

On Wed, Nov 24, 2010 at 5:24 PM, Georg Brandl g.bra...@gmx.net wrote:

 at http://dpo.gbrandl.de/contents, you can look at a version of the 3.2
 docs that has the upcoming commenting feature.  JavaScript is mandatory.

This is awesome!! Thanks for this work, remember to buy you a beer next PyCon!


 Credits go to Jacob Mason, whose GSOC project is responsible for almost all
 of what you see there.  [1]

Ok, two beers.

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] MemoryError... how much memory?

[Facundo Batista]

On Wed, Oct 27, 2010 at 8:27 PM, Nick Coghlan ncogh...@gmail.com wrote:

 If you see MemoryError (5 bytes), the things you go looking for are
 very different from those you look for when you see MemoryError(1
 gajillion bytes). (i.e. for the former, you look for a memory or other
 resource leak, for the latter, you look for the reason your code is
 trying to get 1 gajillion bytes from the OS). If a long-lived server
 isn't crashing but is still getting MemoryError occasionally, problems
 with specific oversized requests are much more likely than a general
 resource leak (as those usually bring the whole process down
 eventually).

Very well explained, you're all right.

Furthermore, our server is fairly complex: we're using quite some
libraries to do different jobs, and one of the approaches (not the
only one) that we're taking to deal with this beast is to analyze its
memory-related behaviour from an external POV (thinking it as a black
box).

So, beyond it's arguable utility, do you think that having that
information could harm us in some way?

Regards,

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] MemoryError... how much memory?

[Facundo Batista]

There are a lot of places where Python or modules do something like:

self-buf = (char *)malloc(size);
if (!self-buf) {
  PyErr_SetString(PyExc_MemoryError, out of memory);

At job, we're having some MemoryErrors, and one thing that we would
love to know, if how much memory it was asking when that happened.

So, I thought about doing something like:

char message[50];
...
self-buf = (char *)malloc(size);
if (!self-buf) {
  snprintf(message, 50, out of memory (asked: %lld), size);
  PyErr_SetString(PyExc_MemoryError, message);


Is any inherent problem in doing this?

May it be a good idea to make it generic, like providing a
PyErr_MemoryError that could accept a message and a number, and stores
that number in the exception objects internals?

Thanks!

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] MemoryError... how much memory?

[Facundo Batista]

On Wed, Oct 27, 2010 at 12:05 PM, Benjamin Peterson benja...@python.org wrote:

 Isn't this usually when you do something like [None]*2**300? In that
 case, wouldn't you know how much memory you're requesting?

It could happen on any malloc. It depends on how much you have free.

Don't think on getting a MemoryError on a python you just opened in
the console. Think about a server with a month of uptime, where you
have all the memory fragmented, etc.


 Also, why is that useful?

It helps to determine why we're having some Memory Errors on our
long-lived server, how is the behaviour when that happens, etc.

Regards,

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Future of 2.x.

[Facundo Batista]

On Wed, Jun 9, 2010 at 8:58 AM, Paul Moore p.f.mo...@gmail.com wrote:

 On that basis I'm +1 on Alexandre's proposal. A 3rd party planning on
 working on a 2.8 release (not that I think such a party currently
 exists) can step up and extract the relevant tickets for their later
 reference if they feel the need. Let's not stop moving forward for the
 convenience of a hypothetical 2.8 development team.

Yes, closing the tickets as won't fix and tagging them as
will-never-happen-in-2.x or something, is the best combination of
both worlds: it will clean the tracker and ease further developments,
and will allow anybody to pick up those tickets later.

(I'm +1 too to Alexandre's proposal, btw)

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Incorrect length of collections.Counter objects / Multiplicity function

[Facundo Batista]

On Thu, May 20, 2010 at 5:59 PM, Gustavo Narea m...@gustavonarea.net wrote:

 Anyone?

The best place to post a bug is the bug tracker [0]: you'll surely
receive proper attention there.

Regards,

[0] http://bugs.python.org/

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Mixing float and Decimal -- thread reboot

[Facundo Batista]

On Fri, Mar 19, 2010 at 5:50 PM, Guido van Rossum gu...@python.org wrote:

 As a downside, there is the worry that inadvertent mixing of Decimal
 and float can compromise the correctness of programs in a way that is
 hard to detect. But the anomalies above indicate that not fixing the

Decimal already has something that we can use in this case, and fits
very nice here: Signals.

Signals represent conditions that arise during computation. Each
corresponds to one context flag and one context trap enabler.

So, if we add a signal like MixedWithFloats, users will have a flag
in the context that they could check to see if a float was mixed in
the operations executed (and if the user set the trap accordingly, an
exception will be raised when the signal happens).

OTOH, returning a float the first time both are mixed is easy to
check... but if it has downsides, and we prefer to return a Decimal in
that case, note that we have a mechanism in Decimal we can use.

Furthermore, in case we want to ease the transition we can do the following:

- add this signal

- set *by default* the trap to raise an exception when float and
Decimal is mixed

So, the behaviour will be the same as we have now, but users can
easily change it.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Decimal - float comparisons in py3k.

[Facundo Batista]

On Tue, Mar 16, 2010 at 9:41 AM, Mark Dickinson dicki...@gmail.com wrote:

 On the one hand there's something to be said for maintaining a clean
 separation between the float and Decimal types, allowing only explicit
 conversions from one to the other;  mixed-type arithmetic between
 floats and Decimals was very deliberately not permitted in the
 original PEP, and that's unlikely to change in a hurry.  On the other

But, to be fair, we didn't have true value of the float at that time.

I'm +0 to allow these comparisons, being Decimal(1)  .3 the same as
Decimal(1)  Decimal.from_float(.3)

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Improved Traceback Module

[Facundo Batista]

On Thu, Jan 28, 2010 at 10:33 AM, Benjamin Schweizer
we...@benjamin-schweizer.de wrote:

 I've updated the traceback.py module; my improved version dumps all
 local variabes from the stack trace, which helps in debugging rare
 problems. You can find details in my latest blog post here:

This is like the django traceback if debug mode is on?

I would love to get tracebacks with all variables in all levels of the stack.

However, this may be too much information for standard tracebacks, so
what do you think to enable it on demand? Like setting a flag or
importing a module at the beginning of the file?

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] bug triage

[Facundo Batista]

On Wed, Jan 6, 2010 at 8:19 AM, Chris Withers ch...@simplistix.co.uk wrote:

 Is there a high volume of incoming bugs to the Python tracker?
 If so, I'd like to help with triaging. I think I have all the necessary
 access, what I'm missing is the knowledge of how to set myself up to get
 notifications of new bugs...

Not notifications, but maybe a way to have a higher look of them for
easy selection:

  http://www.taniquetil.com.ar/cgi-bin/pytickets.py

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] PEP 3003 - Python Language Moratorium

[Facundo Batista]

On Tue, Nov 3, 2009 at 2:35 PM, Guido van Rossum gu...@python.org wrote:

 fierce discussion here on python-dev. It's important to me that if if
 this is accepted it is a rough consensus decision (working code we

+1 to the PEP.

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] surprised to ++ and --

[Facundo Batista]

2009/9/23 Wee Binn weeb...@gmail.com:

 I know that there is no ++ or -- operator in python, but if var++
 or something like that in my code(you know, most of C/C++ coders may like
 this),there is nothing wrong reported and program goes on just like
 expected!!
 This is obscure, maybe a bug.

You can not write var++:

 var = 5
 var++
   File ipython console, line 1
 var++
  ^
SyntaxError: invalid syntax


-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Avoiding file descriptors leakage in subprocess.Popen()

[Facundo Batista]

On Sat, Jun 13, 2009 at 9:40 AM, Facundo
Batistafacundobati...@gmail.com wrote:

 How about a nice 'n shiny context wrapper for the pipe:

 I'll do this!

 Thank you for the suggestion!

Boo, I can not take this approach, neither the previous one.

The reason is very specific for subprocess.py... after creating the
FDs, it forks(), and the behaviour of when closing which descriptors
are different for the parent and child processes.  If I take Christian
approach, the test just hangs. One drawback of the with usage is
that it closes both FDs at the same time... and in this case this may
be a problem, as they're used and closed by different processes in
different times... don't know.

I also tried the approach of wrapping the FDs with a file object...
this *almost* work... but in the case of a problem in the child
process, when a traceback should be written through the pipe to the
parent, nothing happens (it seems that the GC just closes the object
and the info is not transferred).

So, I'll stick to the code I submitted to the bug, because even if
it's ugly it works.

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Avoiding file descriptors leakage in subprocess.Popen()

[Facundo Batista]

On Fri, Jun 12, 2009 at 9:06 PM, Christian Heimesli...@cheimes.de wrote:

 How about a nice 'n shiny context wrapper for the pipe:

I'll do this!

Thank you for the suggestion!

BTW, as this is a good way of avoiding the FD leakage, should this
context wrapper for pipe() be in the stdlib?

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Avoiding file descriptors leakage in subprocess.Popen()

[Facundo Batista]

In a long lived process at work, we started leaking file descriptors.

The problem were that subprocess.Popen._execute_child() method creates
two files descriptors through a call to os.pipe(), and after some work
it closes them. But an os.read() on the descriptor was interrupted
(EINTR), so an exception was raised, and the descriptors were not
closed... leakage!

This problem is easy to fix (I have a patch that fixes it, all tests
pass ok, see http://bugs.python.org/issue6274).

So, why this mail? I just think that the fix is ugly... it's not
elegant. It has the following structure:


errpipe_read, errpipe_write = os.pipe()
try:
try:
.
.
.
.
.
.
finally:
os.close(errpipe_write)
.
.
.
finally:
os.close(errpipe_read)


I just don't like a huge try/finally... but as FDs are just ints, do
you think is there a better way to handle it?

Thank you!!

Regards,

--
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Regexp 2.7

[Facundo Batista]

2009/3/7 Antoine Pitrou solip...@pitrou.net:

 Matthew Barnett has been doing a lot of work on the regular expressions engine
 (it seems he hasn't finished yet) under http://bugs.python.org/issue2636.
 However, the patches are really huge and touch all of the sre internals. I
 wonder what the review process can be for such patches? Is there someone
 knowledgeable enough to be able to review them?

All test cases run ok? How well covered is that library?

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Tracker archeology

[Facundo Batista]

2009/2/10 Daniel (ajax) Diniz aja...@gmail.com:

 If anyone is interested in being added as nosy for any category of
 bugs, let me know and I'll do that as I scan the tracker.

Anything related to Decimal, add me.

Thanks!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Examples in Py2 or Py3

[Facundo Batista]

2009/1/29 Senthil Kumaran orsent...@gmail.com:

 And for blocks of code

 # this for python 3.0
 # this is for python 2.6

Too much work, ;)

Seriously, most probably people will forgot to add that after the
third example...

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] PEP 3142: Add a while clause to generator expressions

[Facundo Batista]

2009/1/19 Gerald Britton gerald.brit...@gmail.com:

 Could you please expand on your thoughts about possible confusion?
 That is, how do you see a programmer becoming confused if this option
 were added to the syntax.

My main concern about confusion is that you're adding a while that
actually will behave like a break in the for.

I know that with while you read it better, but the meaning is
different in the generator/list comprehension for loop.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] another Python Bug Day?

[Facundo Batista]

2009/1/6 Simon Cross hodgestar+python...@gmail.com:

 It'd also be nice if there could be some committers around on IRC to

All those who are working in the bug day, should be in #python-dev
during the work...

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Roundup version numbers

[Facundo Batista]

Hi!

To craete this issue compilation [0] I use roundup through its web interface.

For example, to know which version names corresponds to each number, I
consulted them through:

  http://bugs.python.org/version

But since two weeks ago, this list was trimmed down. I think that it
was to not be able to submit bugs for older Python versions, which is
great, but there're some bugs assigned to older versions (for example,
[1]).

So, question:

Should I use another way to query the version number-name relationship
(to see them all)? Or those issues that point to older Python versions
should be updated?

Thank you!!


[0] http://www.taniquetil.com.ar/cgi-bin/pytickets.py
[1] 
http://bugs.python.org/iss...@search_text=title=@columns=titleid=@columns=idcreation=creator=activity=@columns=activity@sort=activityactor=nosy=type=components=versions=4dependencies=assignee=keywords=priority=@group=prioritystatus=1@columns=statusresolution=@pagesize=50@startwith=0@queryname=@old-queryname=@action=search

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Roundup version numbers

[Facundo Batista]

2009/1/5 Martin v. Löwis mar...@v.loewis.de:

 All existing associations between versions and issues stay as they are.
 I don't quite understand what the problem is. Yes, the versions were
 retired (in roundup speak), and yes, issues that were originally
 associated with the retired versions stay associated. So what is the
 problem with that?

The problem is that I don't have a way to find out the relation
number-name for the versions (see below).


 (there might also be an XML-RPC interface to do that). OTOH, if you had
 downloaded the list of versions once, you can trust that each id

I didn't download the list versions once, so far I got it everytime
from the server (it was cheap, because it's short, and I don't have
the issue of the local copy becoming obsolete if something changed).

How I donwloaded it everytime? I went to

  http://bugs.python.org/version

and parsed the id and name for each line. But I can not do this anymore.


 continues to mean what it meant on creation, so you might want to look
 only for updates (i.e. newer ids).

I guess I could do this, if there's no other way to have all the (id,
name) pairs for all the existing version values.

Thank you!

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] RELEASED Python 3.0 final

[Facundo Batista]

2008/12/4 A.M. Kuchling [EMAIL PROTECTED]:

 * that there will be a Python 2.7 that will incorporate what we learn from
  people trying to port,
 * that 3.1 will rearrange the standard library in mostly-known ways, and
 * that we expect people to use 3.0 mostly for compatibility testing,
  not going into serious production use until 3.1 or maybe even 3.2.

I think that would be fantastic to have a small set of straightforward
sentences like these, to transmit the most important stuff.

For my part, when it's fixed, I will translate them to spanish and
propagate them.


 (The details are open to discussion, of course.)

I think those are fine. I would add something about the migration
path, something like If you want to start testing your library/system
in 3.0, you should first use Python 2.6, see migration details [here]

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] 2.6.1 and 3.0

[Facundo Batista]

2008/11/18 Martin v. Löwis [EMAIL PROTECTED]:

 While I'm happy that Barry has automated his part to a high degree,
 my part is, unfortunately, much less automated. I could personally
 automate the build process a bit more, but part of it is also testing
 of the installers, which is manual.

Martin, maybe we can help you with the installers testing.

While I don't have a clue about compiling complex software in Windows
(and also want to stay away from that), I have a virtualbox with a win
xp in my workstation, so I could try an installer.

Maybe you could put a wiki page somewhere with a small recipe about
what to look when testing an installer, and then produce all the
versions, upload to it, and alert us here. So we go, download one of
them, try it, and then mark it as tested with our name (maybe we can
look after two or three testers per installer).

I don't know if this will be quicker, but surely will lower your
workload regarding this, which is a good thing.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] 2.6.1 and 3.0

[Facundo Batista]

2008/11/17 Barry Warsaw [EMAIL PROTECTED]:

 Martin suggests, and I agree, that we should release Python 3.0 final and
 2.6.1 at the same time.  Makes sense to me.  That would mean that Python
 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!).

2.6.1 only two months after 2.6? Why so quickly?

Anyway, I don't see any added value in the synchronization, so taking
in consideration all the effort you're putting in these releases, I
would just want to minimize your workload... which is easier to you?
doing both at the same time or not?

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] A statistic for Python tickets

[Facundo Batista]

Hi all! I generated this info for other list, thought that it could be
valuable to share it here...

I've been collecting some statistics since January, as I'm concerned
about the issue of tickets quantity just getting higher.

I've been saving twice a day (everytime I generate this [0] info), the
following numbers for *still open* tickets:

 - How many tickets are open since: less than one week, between one
week and two months, between two months and a year, more than a year.

- How many tickets don't have any comment in the same periods.

- How many tickets per keyword.

- How many tickets per version.

I just graphed the first number how many tickets are open since
the different periods. As you can see here [1], the tickets that are
open since less than a week remain more or less constant. Those opened
between a week and two months even seem to go down a little in the
last weeks.

But those opened more than two months ago just increase.

Looking at this information, and applying some experience with the
tickets, my conclusion is that when a ticket is fresh, is easier to
handle it, but when a ticket starts to getting older, it just stalls.

I can think now two reasons for this behaviour: the first is that in
some tickets when a discussion arises, sometimes it gets to a dead
point, from where it's very difficult to get out. The second is that
in a lot of cases more info is needed from the OP, and the older the
ticket, the less responsive is the OP.

In general, I think that a lot of older tickets drain a lot of effort
from developers, but I don't know which is the best way to handle
this, :(

Note: the jump that appears in the numbers at the beginning was an
import of old SourceForge tickets to the new system, IIRC.

Regards,

[0] http://www.taniquetil.com.ar/cgi-bin/pytickets.py
[1] http://www.taniquetil.com.ar/facundo/stathist.png

--
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] Proposed Python 3.0 schedule

[Facundo Batista]

2008/10/6 Raymond Hettinger [EMAIL PROTECTED]:

 15-Oct-2008 3.0 beta 4
 05-Nov-2008 3.0 rc 2
 19-Nov-2008 3.0 rc 3
 03-Dec-2008 3.0 final

 Given what still needs to be done, is this a reasonable schedule?  Do  we
 need two more betas?

 Yes to both questions.

I agree with you here.


 I'm seeing that people are just starting to download and play with 3.0.
 I expect that we'll start getting more feedback on conversion issues,
 the C API, screwy interactions with operating systems, bytes/text issues,
 unanticipated interactions with other tools, etc.  Each user will stress
 it in new ways and perhaps reveal a bunch of little integration issues
 and documentation issues.  Those little fixups way go a long way toward
 establishing a good first impression and reputation for 3.0 from the outset.

And maybe also here, but bounded.

I don't want to keep deferring 3.0 months and months, I prefer to have
a redesigned schedule now, and stick to it as much as possible, even
if the 3.0 version is not as robust as we would want.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] 3.1 focus (was Re: for __future__ import planning)

[Facundo Batista]

2008/10/5 Martin v. Löwis [EMAIL PROTECTED]:

 foobar-1.0-py2.6.tar.gz
 foobar-1.0-py3.0.tar.gz

 More likely, in this way:

 foobar-1.0-py2.tar.gz
 foobar-1.0-py3.tar.gz

 How do you implement this in distutils? People probably won't rename
 the files from how sdist names them. So it's more likely that they
 come up with things like

Sorry, I was not advising that structure, just mentioning that if
you'll follow it, don't include the minor version, just the major one.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] 3.1 focus (was Re: for __future__ import planning)

[Facundo Batista]

2008/10/5 Kevin Teague [EMAIL PROTECTED]:

 on Python 3 after running it through 2to3. The source code is different so
 that to me suggests different version numbers - but the API will be the
 same, so maybe the same version number should be used? That is should there
 be?

 foobar-1.0-py2.6.tar.gz
 foobar-1.0-py3.0.tar.gz

More likely, in this way:

foobar-1.0-py2.tar.gz
foobar-1.0-py3.tar.gz


 Or should it be something like?

 foobar-1.0.tar.gz # Python 2
 foobar-1.1.tar.gz # Python 3

The problem here is that I can foresee libs or apps that have a mixed
path, starting to support Py 3 at some point, and deprecating the Py 2
support after a while:

foobar-1.0.tar.gz   # Py 2
foobar-1.1.tar.gz   # Py 2  3
foobar-1.2.tar.gz   # Py 2  3
foobar-1.3.tar.gz   # Py 2  3
foobar-1.4.tar.gz   # Py 2  3
foobar-1.5.tar.gz   # Py 3

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] 3.1 focus (was Re: for __future__ import planning)

[Facundo Batista]

2008/10/4 Brett Cannon [EMAIL PROTECTED]:

 So the mailing list is a good idea. Perhaps it should just be
 python-porting so that it can also be used for people who have
 problems with minor releases?

+1. I'd try to help on that list, also.

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] Not releasing rc1 tonight

[Facundo Batista]

2008/9/4 Raymond Hettinger [EMAIL PROTECTED]:

 Can I go ahead with some bug fixes and doc improvements
 or should I wait until after Friday?

Doc improvements: go ahead.

Bug fixes: the patchs should be revised by other developer.

(I'll be hanging around in #python-dev today and tomorrow, btw, ping
me if I can help you)

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Stable / unstable buildbots

[Facundo Batista]

2008/8/28 Barry Warsaw [EMAIL PROTECTED]:

 bots we should trust to judge the health of the trees.  I don't think the
 current list needs to be set in stone, and in fact several of the stable
 bots have had simple svn or other non-tree related problems for a while.

Maybe a good requisite to move a buildbot from unstable to stable is
to find a champion for it. I mean, something that can test on that
platform and cares enough about it to, or fix the issue
himself/herself, or find who broke it and bother the responsible until
it gets fixed.

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Stable / unstable buildbots

[Facundo Batista]

2008/8/28 Antoine Pitrou [EMAIL PROTECTED]:

 By that metric, I fear that the only remaining buildbots would be the
 Linux/Windows x86/x64 ones. I'm not sure anyone here, for example, cares 
 really

Note that I meant to move from unstable to stable, starting from the
actual state, not to decide again which ones will be stables or
not.

I agree with you in all the other matters.

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Unicode 5.1.0

[Facundo Batista]

2008/8/21 Guido van Rossum [EMAIL PROTECTED]:

 The two, quite separate, questions, then, are (a) how much work would
 it be to upgrade to version 5.1.0 of the database; and (b) would it be
 acceptable to do this post-beta3 (but before rc1). If the answer to
 (b) is positive, Google can help with (a).

Two thoughts:

- In view of jumping to a new standard at *this* point, what I'd like
to have is a comprehensive test suite for unicodedata in a similar
sense to what happens with Decimal... It would be great to have from
the Unicode Consortium a series of test cases (in Python, or in
something we could process), to verify that we support Unicode
properly.

- We always could have a beta4 if it's necessary...

Just my two pesos cents.

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Memory tests in Unicode

[Facundo Batista]

The test_raiseMemError() in test_unicode.py is complicating me the
regression tests: tries to use all the memory in my system, which
starts to swap as crazy, and almost freezes everything. When the test
finishes (always pass ok), I have all the memory flushed so it take a
few seconds to go back to the normal system.

I told myself that this test should run only in some special cases,
but didn't find any flag in regrtest.py (like largefile, or
network), to put this test under.

Are you having also this issue? Do you think that it should run not *always*?

It's ok if I add a flag like memory that will hold Tests that use
large amount of memory. Normally these tests take long to run because
use all your memory and make the system swap?

Thank you!!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] parse_qs and parse_qsl functions

[Facundo Batista]

Hi!

The issue 600362 has two patches (one for 2.6 and the other for 3.0)
that are ready to commit (with a small change in the docs). This
patches relocates the parse_qs and parse_qsl functions into the
urlparse module (urllib.parse in 3k), bringing them from the cgi one.

For backward compatibility, those functions are also accessible from
the cgi module, but in the documentation says that the function was
moved, and you should use it from the urlparse one.

So, we don't have *any* change in the behaviour towards the final user.

Two questions:

- It's ok to do this now or we should wait for 3.1/2.7?

- Should we add a deprecation warning in the cgi module for this functions?

I propose to commit this now, but leave a deprecation warning for the
next release.

Thanks!!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Memory tests in Unicode

[Facundo Batista]

2008/8/16 Antoine Pitrou [EMAIL PROTECTED]:

 If the test does allocate the very large string, it means MemoryError isn't
 raised, which defeats the purpose of the test.

I do *not* want to remove the test.

I just want to execute it *only* when I run -u all or -u memory,
not everytime I run the regression tests.

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Memory tests in Unicode

[Facundo Batista]

2008/8/16 Martin v. Löwis [EMAIL PROTECTED]:

 See bug http://bugs.python.org/issue3556

 If no solution is forthcoming quickly, I recommend to remove/disable the
 test.

The Antoine patch works ok for me, and solves the whole issue.

I'm on linux, if somebody can give it a try in another platform, we
should commit it ASAP...

Thanks!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] [OT] Commit number

[Facundo Batista]

Congratulations to Andrew Kuchling for doing the commit # 2**16

Lover-of-round-numbers--ly yours,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] urllib.quote and unquote - Unicode issues

[Facundo Batista]

2008/7/30 Matt Giuca [EMAIL PROTECTED]:

 2. Default to UTF-8.
 In favour: Matt Giuca, Brett Cannon, Jeroen Ruigrok van der Werven
 Pros: Fully working and tested solution is implemented; recommended by
 RFC 3986 for all future schemes; recommended by W3C for use with HTML;
 UTF-8 used by all major browsers; supports all characters; most
 existing code compatible by default; unquote is inverse of quote.
 Cons: By default, URIs may have invalid octet sequences (not possible
 to reverse).

+1, assuming that if you have a different encoding in the URI you can
pass it as a parameter.

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] us.pycon.org down?

[Facundo Batista]

(sorry for the crossposting)

Do you know what happened with http://us.pycon.org/;?

Thank you!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] [PyCon-Organizers] us.pycon.org down?

[Facundo Batista]

2008/7/3 David Goodger [EMAIL PROTECTED]:

 Jeff fixed it. URL rewriting was off by mistake.

Thanks! :)

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Last bug weekend

[Facundo Batista]

Hi all!

In Python Argentina we get together in two places, Buenos Aires and
Santa Fe, and worked out around 10-12 bugs, which is around the half
of the total for both days, so I'm very happy, :)

We even had a Python logo shaped cake, see, see [1].

Did you participate? What do you think it's the outcome for both days?

Regards,

[1] http://www.taniquetil.com.ar/facundo/imgs/tortalogopy.jpeg

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Disable tests in unittest (issue3202)

[Facundo Batista]

2008/6/25 Justin Mazzola Paluska [EMAIL PROTECTED]:

 The idea behind the patch is that it's sometimes useful to disable
 tests without removing them from the TestCase.  For example, a
 co-worker and I have a module with a few tests that will fail for the
 forseeable future because we haven't had a chance to implement the
 features the tests are testing.  The tracebacks for these not
 implemented yet tests obscure real failures in other tests.

What about TestSkipped? I thought that raising
test_support.TestSkipped should behave like this: you're saying that
you're actually NOT executing the tests, but you say that they are
there.

But a few days ago I needed to comment out a test that previously was
raising this, because it made a buildbot to go red.

How this should behave?

Thanks!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] Issue 2722

[Facundo Batista]

2008/6/21 Neil Muller [EMAIL PROTECTED]:

 Could some one have a look at the suggested fix for issue 2722? While
 not a particularly common problem, it can be an annoyance, and the
 patch looks reasonable.

I'm on it... Python Bug Day!

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] First betas (perhaps) on June 18

[Facundo Batista]

2008/6/13 Barry Warsaw [EMAIL PROTECTED]:

 My proposal is this: I will spin another release this coming Wednesday, June
 18.  If we can get both the 2.6 and 3.0 buildbots green by then, and close
 out all remaining release critical bugs, then Wednesday's release will be
 beta 1.  In that case, I will update PEP 361 and push the entire schedule
 back by 2 weeks to account for our slippage.

Next weekend, 21 and 22, it will be the Python Bug days.

Maybe it's worth to delay the betas one week to include this work?

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] PEP 8 and optional underscores

[Facundo Batista]

2008/6/12 Barry Warsaw [EMAIL PROTECTED]:

  function:: active_count()
  method:: Thread.get_name()
  method:: Thread.is_alive()
  method:: Thread.is_daemon()
  method:: Thread.set_daemon(daemonic)

 +1 on opting for properties in the specific cases here where it makes sense.

I'm +1 too... but which is the normal procedure here?

Should it be...

  2.n : .is_alive()
  2.n+1 : .is_alive() (deprecated), .alive (recommended)
  2.n+2 : .alive

...?

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] bugs.python.org down

[Facundo Batista]

2008/6/12 anton [EMAIL PROTECTED]:

 ping works but http://bugs.python.org giges after a timeout:

I can enter into it.

Also note that my issues showing system [1] was updated 6.5 hours ago,
so it was up at that time (my system goes and get some info twice a
day, you have the last updated info down on that page).

Regards,

[1] http://www.taniquetil.com.ar/cgi-bin/pytickets.py

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] New Developer

[Facundo Batista]

2008/6/6 James Thomas [EMAIL PROTECTED]:

 Hi All,
 I'm a new developer with Python. I have a solid knowledge of both Python and
 C. Are there any tasks that would be suitable for a beginner to the Python
 codebase? I haven't been able to find a list of such tasks on python.org or
 bugs.python.org.

Welcome!

The issue tracker [1] is *the* place to find such tasks! Note that
there're some tasks tagged as easy [2], take a look!

Next week we'll have a Python Bug Weekend [3], it's a good moment to gain speed.

(ah, what is not welcomed are HTML mails)

Regards,

[1] http://bugs.python.org/
[2] 
http://www.taniquetil.com.ar/cgi-bin/pytickets.py?nropag=0priority=0severity=0component=0version=0keyword=6
[3] http://wiki.python.org/moin/PythonBugDay

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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] on Python's tests (and making them better)

[Facundo Batista]

2008/6/6 Benjamin Peterson [EMAIL PROTECTED]:

 I always find it hard to find a test I'm looking for in a directory
 with 365 different tests in it. Also grouping tests by function will
 hopefully help reduce duplication and it more intuitive.

Intuitive to who taking into account which grouping?  Start to group
using *your* intuitive way, and a lot of people will find it
unintuitive.

-1 to group the tests.

Regards,

-- 
. Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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