while sorting those I hope that b3 will still work for those
case.
Will the reasonable range requirement eventually be made mandatory? It does
seem like a good idea.
Will there be an extra beta?
--
Robin Becker
___
Python-Dev mailing list -- pytho
longtime python programmer I wonder if such simple cases are already optimized out in the
produced bytecode; for years I have been avoiding s += 'string' and only recently found out that it was handled as a
special case.
--
Robin Becker
__
t might be impossible as the test might need to actually try and
build _ssl.so.
--
Robin Becker
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/li
On 19/10/2021 11:21, Christian Heimes wrote:
On 19/10/2021 11.57, Robin Becker wrote:
..
For PEP 644 I added new instructions how to build Python 3.10 with custom OpenSSL builds. The instructions should work
on all major Linux distributions. They have been tested on Debian-like and
ssl.so.1.1
/usr/include/openssl/
This all used to work in Python 3.9.x, but I suppose some improvement(s) have
been made.
--
Robin Becker
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python
e pkgutils or pkg_resources to mess with these new-fangled
packages.
Likewise I find that the python statement 'import A' also doesn't fail and A is
a namespace. I feel quite stupid now :(
--
Robin Becker
___
Python-Dev mailing list --
in 3.10.0a7 I occasionally see a problem, but in 3.10.0b1 or b2 I see the problem every
time; the TB ends like this
print(recursiveImport(mn, debug=1))
File "/home/robin/devel/reportlab/REPOS/timpbug/tests/timport-310b1.py", line
36, in recursiveImport
return importlib.impo
ith different values for the target directory; the first
usage seems to succeed.
--
Robin Becker
___
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/pyth
/Pillow/commit/543fa2ceb78103c7ae098900c315748a9283e4d4
Victor
Thanks for that. I might try to build pillow from git and see if that helps.
...--
Robin Becker
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python
On 17/01/2021 13:49, Terry Reedy wrote:
On 1/17/2021 8:05 AM, Stestagg wrote:
Hi Robin
It would be ideal if you could please create a new issue here:
https://bugs.python.org/ <https://bugs.python.org/>
If 'reportlab userguide creation' uses any 3rd party compiled C c
.6 + 0x7f5e8)
#3 0x7f7c9bfbc27a malloc_printerr (libc.so.6 + 0x8727a)
#4 0x7f7c9bfbd64c _int_free (libc.so.6 + 0x8864c)
#5 0x5631260a01dd n/a
(/home/robin/devel/reportlab/.py310/bin/python310 + 0x1401dd)
1) I compile this from source
examples, but I guess the PEPs
will have to do for now. It's unlikely I will need any of this for a while so examples will appear over time.
--
Robin Becker
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-d
verse?
--
Robin Becker
___
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/pytho
If we are still not certain about the exact language to describe match then I
would ask if the 'case' token is really required. It seems that I would prefer
match expr:
pattern0:
block0
pattern1:
block1
.
else:
blockdefault
where the else: clause is optional.
Sorry for noise, but obviously most of my pasted text went wrong; not sure how
to use this modern mailman. I see a syntax error in 3.9a6 with the code
norm=lambda m: m+(m and(m[-1]!='\n'and'\n'or'')or'\n')
___
Python-Dev mailing list -- python-dev@pytho
While testing 3.9a6 in the reportlab package I see this difference from 3.8.2;
I built from source using the standard configure make dance. Is this a real
change?
robin@minikat:~/devel/reportlab/REPOS/reportlab/tests
$ python
Python 3.8.2 (default, Apr 8 2020, 14:31:25)
[GCC 9.3.0] on linux
) after I have
finished backporting PEP 3102 (keyword-only arguments) (issue1745).
Could someone with access rights update the spreadsheet so there won't
be duplicated efforts?
http://spreadsheets.google.com/pub?key=pCKY4oaXnT81FrGo3ShGHGg&g
Fair enough.
Robin
On 30/11/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Robin Bryce schrieb:
> > Yes, especially with the regard to the level you pitch for LSB. I
> > would go as far as to say that if this "contract in spirit" is broken
> >
y to get positive
confirmation I'm using the "Canonical" variant (pun intended)
python -c "from distutils.util import get_platform; print get_platform()"
Tells me nothing about the vendor of my linux distribution. Except,
ironically, when it says ImportError
Cheers,
Robin
viable on more than
linux. Is it unreasonable for a particular vendor to decide that, on
their platform, the will disable Python's packaging conventions ? Is
there any way to keep the peace on this one ?
Cheers,
Robin
On 27/11/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 02
This has an sf number now #1537167, and hopefully a clearer
explanation of what I think the problem is. This is not a duplicate of
the earlier "PEP 302 Fix" thread.
Thanks,
Robin
On 07/08/06, Robin Bryce <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Appologies for the lack of
eagal' module paths is actualy independent of the regresion
I am asserting. Detailed session logs are attatched (following the sf
guidance even though I'm posting to py-dev)
The 'use case' for the importer is: Robin wants to package a default
template file as normal python module
en I spell the usual mutables kluge.
3 statement is positive form
4. I like it
could not find a use of outbound in python source (2.4.3)
[1] http://dictionary.reference.com/search?q=outbound
Robin
___
Python-Dev mailing list
Python-Dev@python.org
http
> But what's the point? We have until Python 3000 anyway.
Ah, my mistake. In my enthusiasm, I foolishly got the time frames of
peps 3103 & 275 mixed up.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
U
is that static/const will evolve as a sibling pep,
does this not make Raymond's suggestion any more appealing, even a
little ?
Is it unacceptable - or impractical - to break the addition of switch
to python in two (minor version separated) steps ?
Robin
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Munn wrote:
> So doing an SVK mirror of the repository should work now, barring
> any further surprises. I'm starting the SVK sync now; we'll see what
> happens.
Confirmed; the SVK mirror took about 18 hours, but it complete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
> Robin Munn wrote:
>
>>> Revision 4077 is fine now. However, the same problem exists in revision
>>> 4284, which has a 0x01 character before the word "add". Same solution:
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Munn wrote:
> Revision 4077 is fine now. However, the same problem exists in revision
> 4284, which has a 0x01 character before the word "add". Same solution:
>
> echo "New commit message goes here" > new-mes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
> Robin Munn wrote:
>
>> echo "New commit message goes here" > new-message.txt
>> svnadmin setlog --bypass-hooks -r 4077 /path/to/repos new-message.txt
>
>
> Thanks for pointing tha
ning the following:
echo "New commit message goes here" > new-message.txt
svnadmin setlog --bypass-hooks -r 4077 /path/to/repos new-message.txt
If there are other, similar problems later in the SVN repository, I was
unable to find them because the SVK mirror process consistently halt
using EXPR as VAR:
~BLOCK
Reads similarly to "with", but leaves the "with" keyword open for
possible use later.
Since it seems traditional for one to introduce oneself upon first
posting to python-dev, my name is Robin Munn. Yes, my name is just one
letter different from R
31 matches
Mail list logo
